How severe is GHSA-7g5f-wrx8-5ccf?

GHSA-7g5f-wrx8-5ccf has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-7g5f-wrx8-5ccf?

GHSA-7g5f-wrx8-5ccf affects the following packages: org.geoserver.community:gs-jdbcconfig (Maven), org.geoserver.community:gs-jdbcconfig (Maven). Ecosystems affected: Maven.

How do I fix GHSA-7g5f-wrx8-5ccf?

Update org.geoserver.community:gs-jdbcconfig to 2.21.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7g5f-wrx8-5ccf is resolved across your whole dependency graph.

How do I detect GHSA-7g5f-wrx8-5ccf in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.community:gs-jdbcconfig. 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-7g5f-wrx8-5ccf 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-7g5f-wrx8-5ccf?

O3 pinpoints whether GHSA-7g5f-wrx8-5ccf 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-7g5f-wrx8-5ccf actively exploited in the wild?

Yes. There are 10 known exploit references for GHSA-7g5f-wrx8-5ccf, including 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-7g5f-wrx8-5ccf?

GHSA-7g5f-wrx8-5ccf is classified as SQL Injection (CWE-89). 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-7g5f-wrx8-5ccf?

A Nuclei detection template exists for GHSA-7g5f-wrx8-5ccf, 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-7g5f-wrx8-5ccf published, and has it been updated?

GHSA-7g5f-wrx8-5ccf was published on February 22, 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.

☕ Maven

GHSA-7g5f-wrx8-5ccf

CRITICAL

GHSA-7g5f-wrx8-5ccf is a critical-severity (CVSS 9.8) SQL Injection vulnerability in org.geoserver.community:gs-jdbcconfig. 10 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-7g5f-wrx8-5ccf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

GeoServer OGC Filter SQL Injection Vulnerabilities

Also known asCVE-2023-25157

Published

Feb 22, 2023

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

10 known

Blast Radius

2 pkgs affected

☕org.geoserver.community:gs-jdbcconfig☕org.geoserver.community:gs-jdbcconfig

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

Impact

GeoServer includes support for the OGC Filter expression language and the OGC Common Query Language (CQL) as part of the Web Feature Service (WFS) and Web Map Service (WMS) protocols. CQL is also supported through the Web Coverage Service (WCS) protocol for ImageMosaic coverages.

SQL Injection Vulnerabilities have been found with:

PropertyIsLike filter, when used with a String field and any database DataStore, or with a PostGIS DataStore with encode functions enabled
strEndsWith function, when used with a PostGIS DataStore with encode functions enabled
strStartsWith function, when used with a PostGIS DataStore with encode functions enabled
FeatureId filter, when used with any database table having a String primary key column and when prepared statements are disabled
jsonArrayContains function, when used with a String or JSON field and with a PostGIS or Oracle DataStore (GeoServer 2.22.0+ only)
DWithin filter, when used with an Oracle DataStore

Patches

GeoSever 2.21.4
GeoServer 2.22.2
GeoServer 2.20.7
GeoServer 2.19.7
GeoServer 2.18.7

Workarounds

Disabling the PostGIS Datastore encode functions setting to mitigate strEndsWith, strStartsWith vulnerabilities (Like filters have no mitigation, if there is a string field in the feature type published).
Enabling the PostGIS DataStore preparedStatements setting to mitigate the FeatureId vulnerability.

References

OGC Filter SQL Injection Vulnerabilities (GeoTools)
OGC Filter Injection Vulnerability Statement (GeoServer Blog)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geoserver.community:gs-jdbcconfig`	all versions	2.21.4
☕Maven	`org.geoserver.community:gs-jdbcconfig`	≥ 2.22.0&&< 2.22.2	2.22.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.