How severe is CVE-2023-25157?

CVE-2023-25157 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-25157?

CVE-2023-25157 affects the following packages: org.geoserver.community:gs-jdbcconfig (Maven), org.geoserver.community:gs-jdbcconfig (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-25157?

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 CVE-2023-25157 is resolved across your whole dependency graph.

How do I detect CVE-2023-25157 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-25157 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2023-25157 actively exploited in the wild?

Yes. There are 10 known exploit references for CVE-2023-25157, 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 is the EPSS score for CVE-2023-25157?

CVE-2023-25157 has an EPSS (Exploit Prediction Scoring System) score of 85.2%, placing it in the 100th 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 CVE-2023-25157?

CVE-2023-25157 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 CVE-2023-25157?

A Nuclei detection template exists for CVE-2023-25157, 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 CVE-2023-25157 published, and has it been updated?

CVE-2023-25157 was published on February 21, 2023 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2023-25157 — gs-jdbcconfig

CRITICALFix: geoserver/geoserver@145a8af

CVE-2023-25157 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. A fix is available for org.geoserver.community:gs-jdbcconfig — see the affected versions and patch details below.

Unfiltered SQL Injection Vulnerabilities in Geoserver

Also known asGHSA-7g5f-wrx8-5ccf

Published

Feb 21, 2023

Updated

Oct 21, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

10 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

85.2%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2023-25157 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,308 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

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`org.geoserver.community:gs-jdbcconfig:2.21.4`
☕Maven	`org.geoserver.community:gs-jdbcconfig`	≥ 2.22.0&&< 2.22.2	2.22.2`org.geoserver.community:gs-jdbcconfig:2.22.2`

Affected Products

1 product · 5 configurations

Application

geoserverosgeo

≥ 2.22.0 && < 2.22.2

range

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.