Skip to main content

CVE-2026-77323MapServer cross-site scripting

Low priorityMedium5.3EPSS not scored yet

CVE-2026-77323 is a cross-site scripting in MapServer, rated medium (5.3 on CVSS 4.0).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

Input is written into a web page without escaping, so an attacker's script runs in the browser of anyone who views it. Script tags in input are written into a page and run in the viewer's browser.

How it is reached

An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

The scored direct impact on the component itself is low. In practice, this kind of flaw lets an attacker act inside a signed-in user's browser session. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade MapServer to 8.6.5 or later.
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

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 this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Web front ends and single-page apps. The flaw sits between a user's browser and the web application.
  • Admin consoles served to a browser. The flaw sits between a user's browser and the web application.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between a user's browser and the web application. An attacker who crosses it can act inside a signed-in user's browser session.

Questions to answer about your own systems

  • Where does MapServer run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.