dbcve.org
MapserverApplication · Osgeo

CVE-2025-59431

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MapServer is a system for developing web-based GIS applications. Prior to 8.4.1, the XML Filter Query directive PropertyName is vulnerably to Boolean-based SQL injection. It seems like expression checking is bypassed by introducing double quote characters in the PropertyName. Allowing to manipulate backend database queries. This vulnerability is fixed in 8.4.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MapServer versions prior to 8.4.1 contain a Boolean-based SQL injection vulnerability in the XML Filter Query directive's PropertyName parameter. Attackers can bypass expression checking by introducing double quote characters in the PropertyName field, enabling manipulation of backend database queries.

MitigationUpgrade MapServer to version 8.4.1 or later to remediate this critical SQL injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MapserverApplication
Affected:= 8.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify MapServer version
    Run 'mapserv -v' or check the mapserv.fcgi/mapserv CGI version banner. Also check any package manager installation (apt, yum, dnf) or source compilation version.
    Affected if The installed version is 8.4.0 or any version prior to 8.4.1 (e.g., 8.2.x, 8.0.x, 7.x series)
  2. Locate MapServer CGI or FastCGI binary
    Find mapserv or mapserv.fcgi binary on the system using 'which mapserv' or by locating in web server cgi-bin directories.
    Affected if MapServer is installed and accessible on the system
  3. Confirm XML Filter Query is in use
    Review MapServer mapfile configurations (*.map files) for the presence of FILTER or XML_FILTER directives, particularly those processing XML-based filter queries with PropertyName parameters.
    Affected if The mapfile contains XML Filter Query configurations that handle PropertyName parameters from external input
  4. Check for exposed MapServer query endpoints
    Inspect web server configuration (Apache/nginx) for CGI/FastCGI mappings to mapserv, and review any WMS/WFS service endpoints that accept filter parameters.
    Affected if MapServer is accessible via HTTP and accepts query parameters that could include Filter Query content

A user is affected if MapServer version 8.4.0 is running and the XML Filter Query feature with PropertyName parameters is enabled and accessible via web requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MapServer to version 8.4.1 or later to remediate this critical SQL injection vulnerability.

Recommended fix High confidence

8.4.1

  1. 1. Back up your current MapServer installation and configuration files
  2. 2. Download MapServer version 8.4.1 from the official MapServer repository or distribution channel
  3. 3. Install or apply the 8.4.1 upgrade following standard MapServer upgrade procedures
  4. 4. Verify the installation was successful
  5. 5. Restart the MapServer service or application to load the updated version
  6. 6. Test that the XML Filter Query functionality works correctly with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mapserver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59431 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59431 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data