Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

GHSA-68cf-j696-wvv9 — gs-wfs

HIGH

GHSA-68cf-j696-wvv9 is a high-severity (CVSS 7.5) vulnerability in org.geoserver:gs-wfs. A fix is available for org.geoserver:gs-wfs — see the affected versions and patch details below.

GeoServer vulnerable to SSRF in TestWfsPost for specific targets, e.g. PHP + Nginx

Published
Jun 10, 2025
Updated
Jun 10, 2025
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Jun 10, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
☕org.geoserver:gs-wfs☕org.geoserver:gs-wfs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Missing checks allow for SSRF to specific targets using the TestWfsPost enpoint.

Mitigation

To manage the proxy base value as a system administrator, use the parameter PROXY_BASE_URL to provide a non-empty value that cannot be overridden by the user interface or incoming request.thomsmith.

Resolution

The TestWfsPost has been replaced in GeoServer 2.25.2 and GeoServer 2.24.4 with a JavaScript Demo Requests page to test OGC Web Services.

References

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.geoserver:gs-wfs≥ 1.0.0&&< 2.24.42.24.4org.geoserver:gs-wfs:2.24.4
☕Mavenorg.geoserver:gs-wfs≥ 2.25.0&&< 2.25.22.25.2org.geoserver:gs-wfs:2.25.2

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver:gs-wfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.geoserver:gs-wfs to 2.24.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68cf-j696-wvv9 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-68cf-j696-wvv9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-68cf-j696-wvv9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Missing checks allow for SSRF to specific targets using the TestWfsPost enpoint. ### Mitigation To manage the proxy base value as a system administrator, use the parameter ``PROXY_BASE_URL`` to provide a non-empty value that cannot be overridden by the user interface or incoming request.[thomsmith](https://github.com/thomsmith). ### Resolution The TestWfsPost has been replaced in GeoServer 2.25.2 and GeoServer 2.24.4 with a JavaScript [Demo Requests](https://docs.geoserver.org/latest/en/user/configuration/demos/index.html#demo-requests) page to test OGC Web Services. ### Ref
O3 Security · Impact-Aware SCA

Is GHSA-68cf-j696-wvv9 in your dependencies?

O3 Security finds GHSA-68cf-j696-wvv9 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
GHSA-68cf-j696-wvv9: gs-wfs SSRF (High 7.5) | O3 Security