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

Back
New CVE Detected

CVE-2026-52854 – Stored XSS – MediaWiki Maps Extension (ProfessionalWiki) before 12.1.3

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-52854 is a stored cross-site scripting (XSS) vulnerability in the Maps extension for MediaWiki, developed by ProfessionalWiki, which is used to render geographic maps from wikitext via the Leaflet mapping service. The flaw allows a wiki user with edit permission to inject executable script that runs in the browser of any user who subsequently views or previews the affected map. It carries a HIGH severity rating (CVSS 8.6) and affects all versions prior to 12.1.3.

Technical details

  • Root cause: the display_map parser function’s overlays parameter accepts attacker-controlled HTML, and the bundled resources/leaflet/jquery.leaflet.js script uses the overlay name directly as a Leaflet layer-control label without HTML-escaping it.
  • Trigger conditions: an authenticated wiki user with standard edit permission crafts wikitext such as {{#display_map:0,0|service=leaflet|overlays=OpenTopoMap.<img src=x onerror="alert(1);">}} and saves or previews the page.
  • Attack vector: Network — exploitation requires no special privileges beyond edit access and no interaction from the victim beyond viewing the page.
  • Impact: script executes in the viewing user’s session, potentially allowing session hijacking, credential theft, or unauthorized actions performed as that user (High confidentiality impact, Low integrity/availability impact per CVSS vector).

Affected software

  • ProfessionalWiki Maps MediaWiki extension — all versions prior to 12.1.3

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade the Maps extension to version 12.1.3 or later, which escapes overlay names before rendering them as Leaflet layer-control labels.
  • If immediate patching isn’t possible: restrict wiki edit permissions to trusted users only, and disable or avoid use of the display_map parser function’s overlays parameter until patched.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: egMapsScriptPath followed by a colon or equals sign.

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