Skip to main content
Menu
CVEs

MapServer reflected XSS in OGC API Features HTML output

CVE-2026-77323Published , updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 8.6.5
Who is exposed
Not reported

Summary

MapServer's OGC API Features HTML output has a reflected cross-site scripting flaw. An attacker can remotely, without logging in, craft a request whose offset or limit values run script when a victim opens the link, and that script runs under the MapServer origin. The attacker could then read browser-session data, act as the victim, and change page content.

Written by a model

Original description

MapServer is a system for developing web-based GIS applications. Prior to 8.6.5, an unauthenticated reflected cross-site scripting vulnerability in OGC API Features collection-items HTML output allows crafted offset or limit query parameter values from raw CGI request handling in src/mapogcapi.cpp to reach template.params.offset or template.params.limit. share/ogcapi/templates/html-bootstrap/collection-items.html inserts those values without quoting or escaping into a script element. A victim who follows a crafted request can have the script element terminated by attacker-controlled markup, causing arbitrary JavaScript to execute under the MapServer origin and enabling access to browser-session data, actions as the victim, and content manipulation. This issue is fixed in 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-77323 (MapServer Reflected XSS via unescaped offset/limit query params injected into <script> in OGC API Features HTML output), 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-77323 (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-77323 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77323 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-288j-mhpj-gmmr
- https://github.com/MapServer/MapServer/pull/7573
- https://github.com/MapServer/MapServer/commit/3bfd0071f74d55b43301ba57f8c4a1425789e0c4
- https://github.com/MapServer/MapServer/commit/47720e835de4d80a602210461d3b52c9f3d5c34c
- https://github.com/MapServer/MapServer/commit/5d2a60c1ffd17839879b7b32ec26f689c9dbf1e9
- 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-77323
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-77323"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

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

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 8

Questions about CVE-2026-77323

Is CVE-2026-77323 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. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-77323?

MapServer: before 8.6.5.

Source: cve.now feed data

How do I fix CVE-2026-77323?

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.