CVE-2021-45474
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 through 1.37, the Special:ImportFile URI (aka FileImporter) allows XSS, as demonstrated by the clientUrl parameter.
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's FileImporter extension (Special:ImportFile) allows injection of malicious JavaScript through the clientUrl parameter. The vulnerable parameter is not properly sanitized before being output in the web page.
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= 35<= 1.37CVSS 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.
-
Check MediaWiki versionAccess Special:Version or inspect LocalSettings.php for the $wgVersion variable to determine the installed MediaWiki versionAffected if Version is 1.37 or lower
-
Confirm FileImporter extension is enabledCheck LocalSettings.php for the require_once or wfLoadExtension call for FileImporter, or look for FileImporter in Special:Version under installed extensionsAffected if FileImporter extension is loaded and appears in the extensions list
-
Verify Special:ImportFile is accessibleNavigate to Special:ImportFile (or index.php?title=Special:ImportFile) in the wiki to confirm the FileImporter special page is accessibleAffected if The special page loads without permission errors
-
Inspect clientUrl parameter handlingSubmit a test request to Special:ImportFile with a crafted clientUrl parameter (such as clientUrl=javascript:alert(1)) and verify whether the value is reflected in the page output without proper encodingAffected if The clientUrl parameter value is reflected in the HTML output unescaped
A user is affected if they are running MediaWiki version 1.37 or lower with the FileImporter extension enabled and the Special:ImportFile page accessible, where the clientUrl parameter is not properly output-encoded.
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.
dbcve · scopedUpgrade MediaWiki to version 1.37.1 or later, or apply the security patch that implements proper output encoding for the clientUrl parameter in the FileImporter extension.
MediaWiki 1.38 or later (if using Fedora, upgrade to a version that ships MediaWiki > 1.37)
- 1. Back up your MediaWiki installation and database before upgrading
- 2. Download MediaWiki version 1.38 or later from the official MediaWiki website or package repository
- 3. Replace the existing MediaWiki files with the new version
- 4. Run the update.php maintenance script to update the database schema if required
- 5. Clear any caches (including parser cache, job queue, and CDN caches if used)
- 6. Verify the Special:ImportFile functionality works correctly and that the clientUrl parameter is now properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45474 — 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-2021-45474 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