Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-54354 – SQL Injection via PostGIS Filter Translation – MapServer 8.4.0 through 8.6.3

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-54354 is a SQL injection vulnerability in MapServer, an open-source platform for building web-based GIS/mapping applications, affecting versions 8.4.0 through 8.6.3. The flaw resides in the PostGIS runtime filter translation logic, which fails to validate attacker-controlled input before embedding it in generated SQL predicates. It carries a CVSS v3.1 base score of 8.2 (High) and is remotely exploitable without authentication.

Technical details

  • Root cause: The msPostGISLayerTranslateFilter() function in src/mappostgis.cpp treats a filter item as numeric whenever a layer is configured with CONNECTIONTYPE POSTGIS and metadata such as gml_<item>_type=Integer. When a field is considered numeric, the generated right-hand value is left unquoted, and msPostGISEscapeSQLParam() only escapes quotes/backslashes rather than validating that the value is a genuine numeric literal.
  • Trigger conditions: A layer must use PostGIS as its connection type and declare numeric-type metadata for the targeted item.
  • Attack vector: Remote, unauthenticated. Exploitable via CGI query parameters (mode=itemquery / mode=itemnquery with the qstring parameter) or via OGC API Features item lookups using the featureId parameter. Non-numeric payloads (e.g., 0 OR 1=1) are concatenated directly into the generated PostgreSQL/PostGIS predicate.
  • Impact: Attackers can bypass query predicates, enumerate unintended records, and perform boolean-based or time-based SQL injection against the backing PostGIS database, increasing database load. The vulnerability does not by itself grant database modification capability.

Affected software

  • MapServer versions 8.4.0 up to (but not including) 8.6.4, when using CONNECTIONTYPE POSTGIS layers with numeric field-type metadata configured.

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L

Mitigation and recommended actions

  • Immediate: Upgrade to MapServer 8.6.4 or later, which fixes the unvalidated numeric filter handling in the PostGIS translation code.
  • If patching is not immediately possible:
    • Restrict or disable public access to CGI itemquery/itemnquery endpoints and OGC API Features item-lookup endpoints on PostGIS-backed layers.
    • Review mapfiles for CONNECTIONTYPE POSTGIS layers with gml_<item>_type=Integer (or similar numeric-type) metadata, and audit database logs for anomalous query patterns or errors indicative of injection attempts.
    • Apply least-privilege database credentials to the MapServer PostGIS connection to limit the blast radius of any successful injection.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge