CVE-2012-1823 — AI Deep Analysis Summary

Q: Who is affected? (Versions/Components)

📦 **Affected**: PHP versions **< 5.3.12** OR **< 5.4.2**. 🌐 **Component**: `php-cgi` binary running in CGI mode. 🏢 **Vendor**: PHP Group / Open Source Community. 📅 Published: May 11, 2012.

Q: Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. 🔑 **Auth**: None required (Remote). ⚙️ **Config**: Requires PHP running in CGI mode. Easy to exploit via HTTP GET/POST parameters. 🎯 Zero-click remote exploitation possible.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed?**: **YES**. 🔧 **Patch**: Upgrade PHP to **≥ 5.3.12** or **≥ 5.4.2**. 📢 **Advisories**: RedHat (RHSA-2012:0568), SUSE (SUSE-SU-2012:0604). Official fixes are long available. 🛡️ Patch immediately.

Updated May 06, 2026

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: PHP CGI Argument Injection. Attackers inject malicious arguments via the command line. <br>💥 **Consequences**: Source code leakage, arbitrary code execution, and sensitive data exposure.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: Improper handling of command-line arguments in `php-cgi`. <br>🔍 **Flaw**: Allows remote injection of parameters (like `-d`) that alter PHP runtime behavior. No strict validation on input arguments.…

Read full answer (login)

Q3Who is affected? (Versions/Components)

📦 **Affected**: PHP versions **< 5.3.12** OR **< 5.4.2**. <br>🌐 **Component**: `php-cgi` binary running in CGI mode. <br>🏢 **Vendor**: PHP Group / Open Source Community. 📅 Published: May 11, 2012.

Q4What can hackers do? (Privileges/Data)

🕵️ **Hackers Can**: <br>1. View source code (`-s` flag). <br>2. Execute arbitrary PHP code via `auto_prepend_file`. <br>3. Access sensitive server info. <br>4. Gain full control if combined with other flaws.…

Read full answer (login)

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. <br>🔑 **Auth**: None required (Remote). <br>⚙️ **Config**: Requires PHP running in CGI mode. Easy to exploit via HTTP GET/POST parameters. 🎯 Zero-click remote exploitation possible.

Q6Is there a public Exp? (PoC/Wild Exploitation)

🔥 **Public Exp?**: **YES**. <br>📜 **PoCs**: Multiple scripts available on GitHub (e.g., `CVE-2012-1823`, `PHP_CVE-2012-1823`). <br>🛠️ **Metasploit**: Modules exist. Wild exploitation is trivial for attackers.…

Read full answer (login)

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1. Visit `http://target/index.php?-s`. <br>2. If source code is displayed, vulnerable! 🚩 <br>3. Use automated scanners for `php-cgi` argument injection patterns.…

Read full answer (login)

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed?**: **YES**. <br>🔧 **Patch**: Upgrade PHP to **≥ 5.3.12** or **≥ 5.4.2**. <br>📢 **Advisories**: RedHat (RHSA-2012:0568), SUSE (SUSE-SU-2012:0604). Official fixes are long available. 🛡️ Patch immediately.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: <br>1. Disable CGI mode; use FastCGI or PHP-FPM. <br>2. Block direct access to `.php` files via web server config (Nginx/Apache). <br>3. Restrict query string parameters.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🚨 **Urgency**: **CRITICAL** (Historically). <br>📅 **Status**: Old vulnerability (2012), but still found on unpatched legacy systems. <br>🎯 **Priority**: **HIGH** for legacy infrastructure.…

Read full answer (login)

Continue exploring

Vulnerability detail Full AI analysis (login) n/a