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

Back
New CVE Detected

CVE-2025-61682 – Stored XSS – Semantic MediaWiki Extension (3.1.0 to <7.0.0)

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2025-61682 is a stored cross-site scripting (XSS) vulnerability in the Semantic MediaWiki extension, a widely used MediaWiki add-on for structured, semantic data. The flaw allows unsanitized values from non-reserved HTML data attributes in wikitext to be inserted directly into the page DOM as HTML, enabling any user with edit permissions to store and execute arbitrary JavaScript. The vulnerability has a CVSS v3.1 base score of 8.6 (High) and affects all deployments running the extension between versions 3.1.0 and 7.0.0.

Technical details

  • Root cause: Semantic MediaWiki’s front-end code parses the data-subtab HTML data attribute as JSON and appends the resulting value directly into the DOM via innerHTML, without sanitizing or encoding it.
  • Trigger conditions: An attacker who can edit a wiki page (a low privilege bar on many wikis, including anonymous or low-trust contributor accounts on open wikis) crafts wikitext containing a specially formed non-reserved data- attribute (e.g., data-subtab) with malicious HTML/JavaScript payload.
  • Attack vector: Network-based (AV:N) and requires no user interaction (UI:N) beyond another user viewing the affected page; the payload is stored persistently and executes for any visitor who renders the compromised page.
  • Impact: Successful exploitation results in stored XSS with high confidentiality impact and low integrity/availability impact — allowing session/cookie theft, credential harvesting, admin account takeover, defacement, or further pivoting within the wiki application, depending on the privileges of the victim who views the page.

Affected software

  • Semantic MediaWiki extension versions >= 3.1.0 and < 7.0.0

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
  • CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)

Mitigation and recommended actions

  • Immediate: Upgrade Semantic MediaWiki to version 7.0.0 or later, which contains the fix for this vulnerability.
  • If immediate patching is not possible:
    • Restrict page-edit permissions to trusted users only, reducing the pool of accounts that could inject a malicious payload.
    • Enable and enforce a strict Content Security Policy (CSP) on the wiki to limit the impact of any injected inline scripts.
    • Monitor recent page edits for unusual data- attribute usage or embedded script-like content as an interim detective control.
    • Review MediaWiki extension configuration to disable or restrict features that render raw/unsanitized HTML from wikitext where feasible.

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