CVE-2025-58360 — AI Deep Analysis Summary

Q: Who is affected? (Versions/Components)

📦 **Affected Versions**: - GeoServer **2.26.0** to **2.26.2** (exclusive of later patches) - GeoServer versions **before 2.25.6** 🔧 **Component**: The WMS (Web Map Service) module.

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

⚡ **Exploitation Threshold**: **LOW**. - **Network**: Remote (AV:N) - **Complexity**: Low (AC:L) - **Auth**: None required (PR:N) - **User Interaction**: None (UI:N) 🎯 Easy to exploit remotely without credentials.

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

🔓 **Public Exploits**: **YES**. Multiple PoCs are available on GitHub (e.g., ProjectDiscovery Nuclei templates, Blackash-CVE-2025-58360). Wild exploitation is likely imminent due to easy access.

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

🔍 **Self-Check**: - Use **Nuclei** with the CVE-2025-58360 template. - Scan for the `/geoserver/wms` endpoint. - Send crafted XML payloads to test for XXE responses. - Check version numbers against the affected list.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. - CVSS Score indicates **High Confidentiality** impact. - No auth required. - Public PoCs exist. 👉 **Action**: Patch immediately or apply WAF rules to prevent file disclosure.

Updated May 06, 2026 CVSS 8.2 · High

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**: GeoServer suffers from an **XML External Entity (XXE)** injection flaw.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-611** (Improper Restriction of XML External Entity Reference).…

Read full answer (login)

Q3Who is affected? (Versions/Components)

📦 **Affected Versions**: 
- GeoServer **2.26.0** to **2.26.2** (exclusive of later patches)
- GeoServer versions **before 2.25.6**
🔧 **Component**: The WMS (Web Map Service) module.

Q4What can hackers do? (Privileges/Data)

💀 **Attacker Capabilities**: 
- **Read Files**: Access arbitrary files on the server (High Confidentiality impact).
- **DoS**: Crash the service or consume resources (Low Availability impact).
- **Privileges**: No authen…

Read full answer (login)

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Exploitation Threshold**: **LOW**. 
- **Network**: Remote (AV:N)
- **Complexity**: Low (AC:L)
- **Auth**: None required (PR:N)
- **User Interaction**: None (UI:N)
🎯 Easy to exploit remotely without credentials.

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

🔓 **Public Exploits**: **YES**. Multiple PoCs are available on GitHub (e.g., ProjectDiscovery Nuclei templates, Blackash-CVE-2025-58360). Wild exploitation is likely imminent due to easy access.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: 
- Use **Nuclei** with the CVE-2025-58360 template.
- Scan for the `/geoserver/wms` endpoint.
- Send crafted XML payloads to test for XXE responses.
- Check version numbers against the affected list.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: **YES**. The vendor has issued a security advisory (GHSA-fjf5-xgmq-5525).…

Read full answer (login)

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: 
- **WAF**: Block XML payloads containing external entity definitions (`<!…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. 
- CVSS Score indicates **High Confidentiality** impact.
- No auth required.
- Public PoCs exist.
👉 **Action**: Patch immediately or apply WAF rules to prevent file disclosure.

Continue exploring

Vulnerability detail Full AI analysis (login) geoserver CWE-611