Skip to main content
Menu
CVEs

MapServer second-order SQL injection in MySQL JOIN handling

CVE-2026-77327Published , updated

6.9MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 8.6.5
Who is exposed
Not reported

Summary

MapServer has a second-order SQL injection flaw in its MySQL JOIN handling, affecting versions before 8.6.5 when MySQL JOIN support is enabled. A remote attacker who can control a source feature attribute, such as data in an imported shapefile or DBF file, can inject SQL that changes the JOIN condition and exposes unrelated records from the MySQL or MariaDB table.

Written by a model

Original description

MapServer is a system for developing web-based GIS applications. Prior to 8.6.5, MapServer's MySQL JOIN implementation in src/mapjoin.c copies the source layer attribute selected by JOIN ... FROM into joininfo->target and inserts it into the query built by msMySQLJoinNext() without parameterization or SQL escaping. When MySQL JOIN support is enabled, an attacker who can control that source feature attribute, including through imported shapefile or DBF data or another untrusted spatial source, can inject SQL operators or expressions that change the intended JOIN predicate. This can bypass the intended key comparison and expose unrelated records from the MySQL or MariaDB JOIN table through output templates, query responses, or downstream application logic. This issue is fixed in version 8.6.5.

What to do

Upgrade to a fixed version: 8.6.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77327 (MapServer: MySQL JOIN second-order SQL injection in src/mapjoin.c), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77327 (entry last updated 2026-11-20):
Affected:
- MapServer MapServer: fixed in 8.6.5
Fixed versions: 8.6.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77327 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77327 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/MapServer/MapServer/security/advisories/GHSA-7624-4mwh-9cxr
- https://github.com/MapServer/MapServer/pull/7547
- https://github.com/MapServer/MapServer/pull/7567
- https://github.com/MapServer/MapServer/commit/b1aa22b1ea4ba4293c0fddea92e01ce0dc18a300
- https://github.com/MapServer/MapServer/commit/f4f95059e2610d431e0b46d75d713cd52b84f64c
- https://github.com/MapServer/MapServer/releases/tag/rel-8-6-5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77327
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77327"}.

Affected versions

cve.now Index

42Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 8

Questions about CVE-2026-77327

Is CVE-2026-77327 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-77327?

MapServer: before 8.6.5.

Source: cve.now feed data

How do I fix CVE-2026-77327?

Upgrade to a fixed version: 8.6.5.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.