dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-10354

MEDIUM · 5.1 CVSS v4.0 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Scripting (XSS) vulnerability reflected in Semantic MediaWiki. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending them a malicious URL using the '/index.php/Speciaal:GefacetteerdZoeken' endpoint parameter. This vulnerability can be exploited to steal sensitive user data, such as session cookies, or to perform actions on behalf of the user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Reflected XSS vulnerability in Semantic MediaWiki's faceted search endpoint ('/index.php/Speciaal:GefacetteerdZoeken'). User-supplied input in a URL parameter is reflected in the HTTP response without proper output encoding, allowing injection of arbitrary JavaScript that executes in victim's browser context.

MitigationApply vendor patch or upgrade to latest Semantic MediaWiki version; alternatively, implement output encoding/sanitization for all user input in the affected endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Semantic MediaWiki is installed
    Check for the presence of the Semantic MediaWiki extension in your MediaWiki installation directory (typically in /extensions/SemanticMediaWiki or via composer). Alternatively, check the Special:Version page on your wiki.
    Affected if Semantic MediaWiki extension is present in the MediaWiki installation
  2. Determine the installed Semantic MediaWiki version
    Visit Special:Version on your wiki and locate the Semantic MediaWiki entry, or check the composer.json file in the extension directory for the version number.
    Affected if The installed version is older than the patched version (the vendor has not specified an exact version range; compare to the latest patched release)
  3. Verify the faceted search endpoint is accessible
    Attempt to access the URL path '/index.php/Special:FacetedSearch' or the Dutch variant '/index.php/Special:GefacetteerdZoeken' on your wiki server.
    Affected if The endpoint responds with a search interface, indicating the faceted search feature is enabled
  4. Check for lack of input sanitization in the endpoint
    Review the source code of the SpecialFacetedSearch or equivalent handler class in the extension. Look for the code path that processes URL parameters and reflects them into the HTML output without using htmlspecialchars() or equivalent encoding.
    Affected if User-supplied URL parameters are directly reflected in the HTTP response without proper output encoding

Your wiki is affected if it runs Semantic MediaWiki with the faceted search endpoint enabled and the installed version lacks the patch for CVE-2025-10354, allowing unsanitized URL parameter reflection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch or upgrade to latest Semantic MediaWiki version; alternatively, implement output encoding/sanitization for all user input in the affected endpoint.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10354 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10354 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data