# CVE-2023-43795: WPS Server Side Request Forgery in GeoServer

> Attackers can exploit Server Side Request Forgery in GeoServer's Web Processing Service to access internal resources or bypass security controls.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Oct 2023
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5pr3-m5hm-9956

## What is CVE-2023-43795?

CVE-2023-43795 is a high-severity server-side request forgery vulnerability in geoserver, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GeoServer is an open source software server written in Java that allows users to share and edit geospatial data. The OGC Web Processing Service (WPS) specification is designed to process information from any server using GET and POST requests. This presents the opportunity for Server Side Request Forgery. This vulnerability has been patched in version 2.22.5 and 2.23.2.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2023-43795?

4 open source packages ship an affected version, including org.geoserver.extension:gs-wps-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.geoserver.extension:gs-wps-core` | Maven | All versions | 2.22.5 |
| `org.geoserver.extension:gs-wps-core` | Maven | All versions | 2.22.5 |
| `org.geoserver.extension:gs-wps-core` | Maven | From 2.23.0 | 2.23.2 |
| `org.geoserver.extension:gs-wps-core` | Maven | From 2.23.0 | 2.23.2 |

Products: Osgeo Geoserver.

## How do I fix CVE-2023-43795?

Upgrade org.geoserver.extension:gs-wps-core to a fixed version for your release line: 2.22.5 or 2.23.2.

## Is CVE-2023-43795 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43795 exists.

Public exploit code:

- GeoServer WPS - Server Side Request Forgery (nuclei): http/cves/2023/CVE-2023-43795.yaml

## Other vulnerabilities in geoserver

- [CVE-2023-25157](https://insights.sbomify.com/CVE-2023-25157/): Unfiltered SQL Injection Vulnerabilities in Geoserver (critical 9.8)
- [CVE-2024-34711](https://insights.sbomify.com/CVE-2024-34711/): GeoServer has improper ENTITY_RESOLUTION_ALLOWLIST URI validation in XML Processing (SSRF) (critical 9.3)
- [CVE-2023-41339](https://insights.sbomify.com/CVE-2023-41339/): Unsecured WMS dynamic styling sld=<url> parameter affords blind unauthenticated SSRF in GeoServer (high 8.6)
- [CVE-2024-29198](https://insights.sbomify.com/CVE-2024-29198/): GeoServer Vulnerable to Unauthenticated SSRF via TestWfsPost (high 7.5)
- [CVE-2025-30145](https://insights.sbomify.com/CVE-2025-30145/): GeoServer has an Infinite Loop Vulnerability in Jiffle process (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-43795 and fix it if it is affected.

What it is: CVE-2023-43795 is a high-severity server-side request forgery vulnerability in geoserver, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43795 exists.

Affected packages and fixed versions:
- org.geoserver.extension:gs-wps-core (Maven): affected all versions; fixed in 2.22.5
- org.geoserver.extension:gs-wps-core (Maven): affected all versions; fixed in 2.22.5
- org.geoserver.extension:gs-wps-core (Maven): affected from 2.23.0; fixed in 2.23.2
- org.geoserver.extension:gs-wps-core (Maven): affected from 2.23.0; fixed in 2.23.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/CVE-2023-43795/ (Markdown: https://insights.sbomify.com/CVE-2023-43795/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-43795
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-43795
- OSV: https://osv.dev/vulnerability/CVE-2023-43795

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-43795/
Summaries are generated and may contain mistakes; the official description above is the record.