CVE-2024-25995 — AI Deep Analysis Summary

Q: Who is affected? (Versions/Components)

🏭 **Vendor**: PHOENIX CONTACT (Germany). 📦 **Product**: CHARX SEC-3000 (AC Charging Controllers). ⚠️ **Affected**: Versions **prior to v1.5.1**.

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

📉 **Threshold**: **LOW**. 🌐 **Access**: Network-based (AV:N). 🔑 **Auth**: None required (PR:N). 👀 **UI**: No user interaction needed (UI:N). Easy to exploit remotely.

Q: Is there a public Exp? (PoC/Wild Exploitation)

🔍 **Public Exploit**: **No**. 📄 **PoC**: None listed in current data. ⚠️ **Risk**: Despite no public PoC, the low exploitation barrier means wild exploitation is highly likely soon.

Q: How to self-check? (Features/Scanning)

🔎 **Self-Check**: 1. Verify firmware version is **< v1.5.1**. 2. Check if configuration endpoints are accessible without login. 3. Scan for PHOENIX CONTACT CHARX SEC-3000 devices on the network.

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

🛠️ **Fix**: Yes. 📥 **Action**: Upgrade to **v1.5.1** or later. 📚 **Source**: Refer to VDE-2024-011 advisory for official patch details.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. 🚀 **Priority**: **Immediate Action Required**. 💡 **Reason**: CVSS 9.8 + No Auth + RCE potential. Patch immediately to prevent total infrastructure takeover.

Updated May 08, 2026 CVSS 9.8 · Critical

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**: A critical Access Control Error in PHOENIX CONTACT CHARX SEC-3000. <br>⚡ **Consequences**: Remote attackers can modify configurations without permission, leading to **Remote Code Execution (RCE)**.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-20** (Improper Input Validation) combined with missing authentication.…

Read full answer (login)

Q3Who is affected? (Versions/Components)

🏭 **Vendor**: PHOENIX CONTACT (Germany). <br>📦 **Product**: CHARX SEC-3000 (AC Charging Controllers). <br>⚠️ **Affected**: Versions **prior to v1.5.1**.

Q4What can hackers do? (Privileges/Data)

💻 **Attacker Actions**: <br>1. Modify system configurations remotely. <br>2. Execute arbitrary code. <br>🔓 **Privileges**: No authentication required.…

Read full answer (login)

Q5Is exploitation threshold high? (Auth/Config)

📉 **Threshold**: **LOW**. <br>🌐 **Access**: Network-based (AV:N). <br>🔑 **Auth**: None required (PR:N). <br>👀 **UI**: No user interaction needed (UI:N). Easy to exploit remotely.

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

🔍 **Public Exploit**: **No**. <br>📄 **PoC**: None listed in current data. <br>⚠️ **Risk**: Despite no public PoC, the low exploitation barrier means wild exploitation is highly likely soon.

Q7How to self-check? (Features/Scanning)

🔎 **Self-Check**: <br>1. Verify firmware version is **< v1.5.1**. <br>2. Check if configuration endpoints are accessible without login. <br>3. Scan for PHOENIX CONTACT CHARX SEC-3000 devices on the network.

Q8Is it fixed officially? (Patch/Mitigation)

🛠️ **Fix**: Yes. <br>📥 **Action**: Upgrade to **v1.5.1** or later. <br>📚 **Source**: Refer to VDE-2024-011 advisory for official patch details.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: <br>1. **Isolate**: Block network access to the device immediately. <br>2. **Restrict**: Apply strict firewall rules to prevent remote configuration access. <br>3.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. <br>🚀 **Priority**: **Immediate Action Required**. <br>💡 **Reason**: CVSS 9.8 + No Auth + RCE potential. Patch immediately to prevent total infrastructure takeover.

Continue exploring

Vulnerability detail Full AI analysis (login) PHOENIX CONTACT CWE-20