Threats / OSGeo / CVE-2025-58360
CVE-2025-58360
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
OSGeo GeoServer vulnerability
OSGeo GeoServer improperly restricts XML external entity references in WMS GetMap requests, allowing attackers to define malicious external entities.
Verdict
Today item — known-exploited.
An unauthenticated attacker can exploit XXE via the /geoserver/wms GetMap endpoint to access local files, trigger server-side requests, or cause denial of service. Active exploitation in the wild increases urgency.
CISA KEV Yes · 2025-12-115EPSS 0.64874 (verify live)6Exploit Public PoC7CVSS 8.23CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
131 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-11).
Probability (EPSS)
EPSS 0.64874 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L) · Affected: OSGeo, GeoServer. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-611 XML External Entity (XXE) — weakness family: Web / client.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 16 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a WMS GetMap request containing XML with a malicious external entity definition pointing to a local file or internal service.
Business
Sensitive configuration files, credentials, or internal system information becomes accessible to the attacker.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use the XXE vulnerability to make the GeoServer instance perform requests to internal systems or external attacker-controlled servers.
Business
Internal network reconnaissance occurs and the organization's infrastructure is mapped by adversaries.
3
Lateral reach — past segmentation narrative 3
Attacker
I submit deeply nested or billion-laughs XML payloads through the GetMap endpoint to exhaust server resources.
Business
GeoServer becomes unavailable, disrupting mapping and geospatial services that depend on the platform.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05