> 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.md).

# CMS Exploitation

CMS exploitation methodology for WordPress, Drupal, Tomcat, phpMyAdmin, Jenkins, admin panels, file upload RCE, LFI-to-RCE, authentication bypass, plugin vulnerabilities, and exposed web applications.

CMS and admin panel exploitation notes focused on enumeration, authentication bypass, plugin abuse, file upload RCE, LFI-to-RCE, command execution, and reverse shell delivery.

## CMS Exploitation Workflow

1. Identify the application, framework, CMS, version, plugins, themes, modules, and exposed admin panels.
2. Enumerate users, login behavior, backup files, upload features, API routes, debug pages, and public configuration leaks.
3. Check default credentials, weak passwords, password reset flows, session handling, and authentication bypasses.
4. Validate known CVEs, plugin vulnerabilities, LFI-to-RCE chains, command injection, and file upload paths.
5. Convert access into a controlled web shell or reverse shell while preserving the exact exploit path.
6. Document credentials, payloads, proof of concept, and post-exploitation handoff clearly.

## Focused Sections

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-wordpress" style="color:$primary;">:wordpress:</i></h3></td><td><h4>WordPress</h4></td><td>WordPress pentesting notes for enumeration, WPScan, plugin discovery, xmlrpc.php brute force, authenticated RCE, vulnerable plugins, LFI, and leaked credentials.</td><td><a href="/cms/wordpress-cms-exploitation.md">WordPress</a></td></tr><tr><td><h3><i class="fa-database" style="color:$primary;">:database:</i></h3></td><td><h4>phpMyAdmin</h4></td><td>phpMyAdmin exploitation notes for version-specific RCE, LFI-to-RCE, session file abuse, command injection, internal port discovery, and reverse shells.</td><td><a href="/cms/phpmyadmin-cms-exploitation.md">phpMyAdmin</a></td></tr><tr><td><h3><i class="fa-server" style="color:$primary;">:server:</i></h3></td><td><h4>Tomcat</h4></td><td>Apache Tomcat exploitation notes for manager access, default credential brute force, WAR payload deployment, text manager abuse, and reverse shells.</td><td><a href="/cms/tomcat-cms-exploitation.md">Tomcat</a></td></tr><tr><td><h3><i class="fa-drupal" style="color:$primary;">:drupal:</i></h3></td><td><h4>Drupal</h4></td><td>Drupal pentesting notes for Droopescan enumeration, password reset request manipulation, Drupal 7 RCE, CVE-2018-7602 exploitation, and reverse shells.</td><td><a href="/cms/drupal-cms-exploitation.md">Drupal</a></td></tr><tr><td><h3><i class="fa-floppy-disk" style="color:$primary;">:floppy-disk:</i></h3></td><td><h4>Duplicati</h4></td><td>Duplicati exploitation notes for SQLite configuration secrets, login authentication bypass, passphrase recovery, backup restore abuse, and sensitive file extraction.</td><td><a href="/cms/duplicati-cms-exploitation.md">Duplicati</a></td></tr><tr><td><h3><i class="fa-server" style="color:$primary;">:server:</i></h3></td><td><h4>Nostromo</h4></td><td>Nostromo exploitation notes for CVE-2019-16278 remote command execution, reverse shell delivery, HomeDirs configuration review, and protected user content discovery.</td><td><a href="/cms/nostromo-cms-exploitation.md">Nostromo</a></td></tr><tr><td><h3><i class="fa-helmet-safety" style="color:$primary;">:helmet-safety:</i></h3></td><td><h4>HardHat C2</h4></td><td>HardHat C2 exploitation notes for JWT authentication bypass, admin token crafting, TeamLead user creation, ImplantInteract terminal abuse, and RCE.</td><td><a href="/cms/hardhatc2-cms-exploitation.md">HardHat C2</a></td></tr></tbody></table>

### Standalone Notes

<table><thead><tr><th data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/cms/joomla-cms-exploitation.md">Joomla</a></td></tr><tr><td><a href="/cms/magento-cms-exploitation.md">Magento</a></td></tr><tr><td><a href="/cms/jenkins-cms-exploitation.md">Jenkins</a></td></tr><tr><td><a href="/cms/chamilo-cms-exploitation.md">Chamilo</a></td></tr><tr><td><a href="/cms/pluck-cms-exploitation.md">Pluck</a></td></tr><tr><td><a href="/cms/wonder-cms-exploitation.md">Wonder</a></td></tr><tr><td><a href="/cms/sqlpad-cms-exploitation.md">SQLPad</a></td></tr><tr><td><a href="/cms/froxlor-cms-exploitation.md">Froxlor</a></td></tr><tr><td><a href="/cms/kibana-cms-exploitation.md">Kibana</a></td></tr><tr><td><a href="/cms/cups-cms-exploitation.md">CUPS</a></td></tr><tr><td><a href="/cms/pandora-cms-exploitation.md">Pandora</a></td></tr><tr><td><a href="/cms/cacti-cms-exploitation.md">Cacti</a></td></tr><tr><td><a href="/cms/umbraco-cms-exploitation.md">Umbraco</a></td></tr><tr><td><a href="/cms/pokermax-cms-exploitation.md">PokerMax</a></td></tr><tr><td><a href="/cms/backdrop-cms-exploitation.md">Backdrop</a></td></tr><tr><td><a href="/cms/snowfox-cms-exploitation.md">SnowFox</a></td></tr><tr><td><a href="/cms/nibbles-blog-cms-exploitation.md">Nibbles Blog</a></td></tr><tr><td><a href="/cms/ghost-cms-exploitation.md">Ghost</a></td></tr><tr><td><a href="/cms/voting-system-cms-exploitation.md">Voting System</a></td></tr><tr><td><a href="/cms/msfvenom-apk-exploitation.md">APK with Msfvenom</a></td></tr><tr><td><a href="/cms/laravel-cms-exploitation.md">Laravel</a></td></tr><tr><td><a href="/cms/adobe-coldfusion-8-cms-exploitation.md">Adobe ColdFusion 8</a></td></tr><tr><td><a href="/cms/helpdesk-cms-exploitation.md">HelpDesk</a></td></tr><tr><td><a href="/cms/helpdeskz.md">HelpDeskZ</a></td></tr><tr><td><a href="/cms/apache-struts-exploitation-.action.md">Apache Struts</a></td></tr><tr><td><a href="/cms/network-admin-panel-cms-exploitation.md">Network Admin Panel</a></td></tr><tr><td><a href="/cms/httpfileserver-2.3-cms-exploitation.md">HttpFileServer 2.3</a></td></tr><tr><td><a href="/cms/strapi-cms-exploitation.md">Strapi</a></td></tr><tr><td><a href="/cms/prtg-network-monitor-cms-exploitation.md">PRTG Network Monitor</a></td></tr><tr><td><a href="/cms/h2-database-cms-exploitation.md">H2 Database</a></td></tr><tr><td><a href="/cms/daloradius-cms-exploitation.md">DaloRADIUS</a></td></tr><tr><td><a href="/cms/dolibarr-cms-exploitation.md">Dolibarr</a></td></tr><tr><td><a href="/cms/limesurvey-cms-exploitation.md">LimeSurvey</a></td></tr><tr><td><a href="/cms/nvms-1000.md">NVMS-1000</a></td></tr></tbody></table>


---

# 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.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.