Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2023-46818 β€” AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: A PHP Code Injection flaw in ISPConfig's language editor. πŸ’₯ **Consequences**: Attackers can execute arbitrary PHP code, leading to full server compromise via web shells.

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: Lack of input sanitization in the `records` POST parameter sent to `/admin/language_edit.php`. πŸ’‘ **CWE**: Improper Neutralization of Input During Web Page Generation (CWE-79).

Q3Who is affected? (Versions/Components)

πŸ“¦ **Affected**: ISPConfig versions **before 3.2.11p1**. πŸ–₯️ **Component**: The `language_edit.php` module within the admin panel.

Q4What can hackers do? (Privileges/Data)

πŸ”“ **Capabilities**: Hackers can inject malicious PHP payloads. ⚠️ **Impact**: They can write web shells (e.g., `sh.php`) and gain **Remote Code Execution (RCE)** to run system commands.

Q5Is exploitation threshold high? (Auth/Config)

πŸ”‘ **Threshold**: **Medium**. Requires **Admin Authentication** AND the `admin_allow_langedit` setting must be **enabled**. 🚫 Not remote unauthenticated.

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

πŸ”₯ **Exploits**: **Yes**, multiple public PoCs exist. 🐍 Python scripts and Nuclei templates are available on GitHub for automated exploitation.

Q7How to self-check? (Features/Scanning)

πŸ” **Check**: Scan for ISPConfig versions < 3.2.11p1. πŸ“‘ Use Nuclei templates (`CVE-2023-46818.yaml`) to detect the vulnerable endpoint and configuration.

Q8Is it fixed officially? (Patch/Mitigation)

βœ… **Fix**: Officially patched in **ISPConfig 3.2.11p1**. πŸ“₯ **Action**: Upgrade immediately to the latest stable version.

Q9What if no patch? (Workaround)

πŸ›‘ **Workaround**: Disable the `admin_allow_langedit` feature in settings. 🚫 Restrict admin panel access via firewall/WAF if upgrade is delayed.

Q10Is it urgent? (Priority Suggestion)

⚑ **Priority**: **High**. While auth is required, the ease of exploitation (RCE) and availability of automated tools make it critical to patch ASAP.