How severe is GHSA-5pr3-m5hm-9956?

GHSA-5pr3-m5hm-9956 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5pr3-m5hm-9956?

GHSA-5pr3-m5hm-9956 affects the following packages: org.geoserver.extension:gs-wps-core (Maven), org.geoserver.extension:gs-wps-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-5pr3-m5hm-9956?

Update org.geoserver.extension:gs-wps-core to 2.22.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5pr3-m5hm-9956 is resolved across your whole dependency graph.

How do I detect GHSA-5pr3-m5hm-9956 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.extension:gs-wps-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-5pr3-m5hm-9956 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-5pr3-m5hm-9956?

O3 pinpoints whether GHSA-5pr3-m5hm-9956 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5pr3-m5hm-9956 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5pr3-m5hm-9956 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5pr3-m5hm-9956?

GHSA-5pr3-m5hm-9956 has an EPSS (Exploit Prediction Scoring System) score of 67.7%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-5pr3-m5hm-9956?

GHSA-5pr3-m5hm-9956 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-5pr3-m5hm-9956?

A Nuclei detection template exists for GHSA-5pr3-m5hm-9956, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-5pr3-m5hm-9956 published, and has it been updated?

GHSA-5pr3-m5hm-9956 was published on October 24, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-5pr3-m5hm-9956: WPS Server Side Request Forgery vulnerabil…

EPSS Exploitation Probability

via FIRST.org ↗

67.7%probability of exploitation in next 30 days

High Risk99th percentile-21.77%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕org.geoserver.extension:gs-wps-core☕org.geoserver.extension:gs-wps-core

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

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.

Details

This vulnerability requires:

The WPS extension to be installed
The WPS security setting "Disable complex inputs" to be unselected
Security URL checks to be disabled

Impact

This vulnerability presents the opportunity for Server Side Request Forgery.

Mitigation

The ability to reference an external URL location is defined by the WPS standard Execute operation. This operations is defined by an Industry and International standard and cannot be redefined by the GeoServer application in isolation.

To disable complex remote inputs on GeoServer 2.20.5 and GeoServer 2.21.0:

Navigate to Security > WPS Security page
Locate Complex Inputs heading
Select the check box for Disable loading complex inputs from remote references

Resolution

To allow processing of complex inputs safely in GeoServer 2.22.5 and GeoServer 2.23.2:

Navigate to Security > URL Checks
Enable URL Checks are enabled setting
Check the user manual for examples of how to trust specific locations for your external services.

Processing of complex inputs safely is on by default in GeoServer 2.24.0.

References

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geoserver.extension:gs-wps-core`	all versions	2.22.5
☕Maven	`org.geoserver.extension:gs-wps-core`	≥ 2.23.0&&< 2.23.2	2.23.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.extension:gs-wps-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.geoserver.extension:gs-wps-core to 2.22.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5pr3-m5hm-9956 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-5pr3-m5hm-9956 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5pr3-m5hm-9956. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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. ## Details This vulnerability requires: * The WPS extension to be installed * The WPS security setting "Disable complex inputs" to be unselected * Security URL checks to be disabled ### Impact This vulnerability presents the opportunity for Server Side Request Forgery. ### Mitigation The ability to reference an external URL location is defined by the WPS standard Execute operation.

O3 Security · Impact-Aware SCA

Is GHSA-5pr3-m5hm-9956 in your dependencies?

O3 detects GHSA-5pr3-m5hm-9956 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-5pr3-m5hm-9956