FedoraOperating system · Fedoraproject
CVE-2020-25814
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 · uneditedIn MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> tag (or it does not have a href attribute, or it's empty, etc.). The actual result is that the object contains an <a href ="javascript... that executes when clicked.
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 · high confidenceCross-site scripting (XSS) vulnerability in MediaWiki where mw.message().parse() fails to sanitize javascript: URI schemes in link syntax. When an attacker crafts a message containing [javascript:payload xss], the parsed jQuery object retains an executable href attribute that executes JavaScript when clicked.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FedoraOperating system
= 33< 1.31.10>= 1.32.0, < 1.34.4CVSS 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
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MediaWiki versionCheck the file includes/Defines.php for the MW_VERSION constant, or access Special:Version on the wikiAffected if Version is < 1.31.10 OR (>= 1.32.0 AND < 1.34.4)
-
Confirm the vulnerable code path existsSearch the codebase for usage of mw.message().parse() in extensions, skins, or custom JavaScript filesAffected if The mw.message().parse() function is being called and processes user-controlled messages
-
Identify if custom messages use link syntaxReview MediaWiki messages stored in the database (message table) or JSON message files for syntax like [javascript:... text]Affected if Any custom or user-supplied messages contain [javascript: URI links]
-
Check for user-editable content using link syntaxSearch wiki pages, signatures, or user profiles for content containing [javascript: strings in what appears to be link formatAffected if User-editable content contains the [javascript:... link] pattern
You are affected if MediaWiki version is in the vulnerable range (< 1.31.10, or >= 1.32.0 and < 1.34.4) AND any custom messages or user content uses the vulnerable link syntax with javascript: URIs.
Generated from the published advisory. Verify against your own configuration.
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 data1.31.101.34.4
Upgrade MediaWiki to version 1.31.10, 1.34.4, or later to receive the security patch that properly sanitizes javascript: URIs in message parsing.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-25814 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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