# GHSA-68cf-j696-wvv9: GeoServer vulnerable to SSRF in TestWfsPost for specific targets, e.g. PHP + Nginx

> Unauthenticated attackers can exploit Server-Side Request Forgery in GeoServer's TestWfsPost endpoint to access internal resources.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2025

## What is GHSA-68cf-j696-wvv9?

GHSA-68cf-j696-wvv9 is a server-side request forgery vulnerability in org.geoserver:gs-wfs, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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](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.

### References

* [CVE-2024-29198](https://github.com/geoserver/geoserver/security/advisories/GHSA-5gw5-jccf-6hxw) Unauthenticated SSRF via TestWfsPost

## Which versions are affected by GHSA-68cf-j696-wvv9?

4 open source packages ship an affected version, including org.geoserver:gs-wfs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.geoserver:gs-wfs` | Maven | From 1.0.0 | 2.24.4 |
| `org.geoserver:gs-wfs` | Maven | From 1.0.0 | 2.24.4 |
| `org.geoserver:gs-wfs` | Maven | From 2.25.0 | 2.25.2 |
| `org.geoserver:gs-wfs` | Maven | From 2.25.0 | 2.25.2 |

## How do I fix GHSA-68cf-j696-wvv9?

Upgrade org.geoserver:gs-wfs to a fixed version for your release line: 2.24.4 or 2.25.2.

## Is GHSA-68cf-j696-wvv9 being exploited?

There is no known exploitation of GHSA-68cf-j696-wvv9 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-68cf-j696-wvv9 and fix it if it is affected.

What it is: GHSA-68cf-j696-wvv9 is a server-side request forgery vulnerability in org.geoserver:gs-wfs, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-68cf-j696-wvv9 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.geoserver:gs-wfs (Maven): affected from 1.0.0; fixed in 2.24.4
- org.geoserver:gs-wfs (Maven): affected from 1.0.0; fixed in 2.24.4
- org.geoserver:gs-wfs (Maven): affected from 2.25.0; fixed in 2.25.2
- org.geoserver:gs-wfs (Maven): affected from 2.25.0; fixed in 2.25.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-68cf-j696-wvv9/ (Markdown: https://insights.sbomify.com/GHSA-68cf-j696-wvv9/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-68cf-j696-wvv9

---
From sbomify Insights: https://insights.sbomify.com/GHSA-68cf-j696-wvv9/
Summaries are generated and may contain mistakes; the official description above is the record.