Skip to content

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

High severity GitHub Reviewed Published Jun 10, 2025 in geoserver/geoserver • Updated Jun 10, 2025

Package

maven org.geoserver:gs-wfs (Maven)

Affected versions

>= 1.0.0, < 2.24.4
>= 2.25.0, < 2.25.2

Patched versions

2.24.4
2.25.2

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

References

@jodygarnett jodygarnett published to geoserver/geoserver Jun 10, 2025
Published to the GitHub Advisory Database Jun 10, 2025
Reviewed Jun 10, 2025
Last updated Jun 10, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-68cf-j696-wvv9

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.