Advisory record · GHSA-5gw5-jccf-6hxw

GeoServer Vulnerable to Unauthenticated SSRF via TestWfsPost

CVSS 7.5 HighEPSS 0.023 · 83rd percentile

Published by the GitHub Advisory Database at 10 Jun 2025, 14:13 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.geoserver:gs-wfsMaven>=2.0.0, <2.24.4 || >=2.25.0, <2.25.22.24.4, 2.25.2
org.geoserver.web:gs-appMaven>=2.0.0, <2.24.4 || >=2.25.0, <2.25.22.24.4, 2.25.2
Identifiers
GHSA-5gw5-jccf-6hxw · CVE-2024-29198
Weakness (CWE)
CWE-918
Published
10 Jun 2025
Updated
10 Jun 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GeoServer, in the gs-wfs and gs-app Maven packages, versions from 2.0.0 before 2.24.4 and from 2.25.0 before 2.25.2, is vulnerable to server-side request forgery through the Demo request endpoint (TestWfsPost) when Proxy Base URL is not set. An unauthenticated attacker can make the server issue requests, which can be used to probe internal networks and, on cloud instances, to reach sensitive data. Upgrade to 2.24.4 or 2.25.2, which removes the servlet. If upgrading is not possible, set a non-empty PROXY_BASE_URL value that users cannot override, or block access to TestWfsPost in web.xml.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.023, the 83rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:11 UTC First seen by agentprime
  2. 31 Oct 2026, 15:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.