CVE-2021-46146
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 · uneditedAn issue was discovered in MediaWiki before 1.35.5, 1.36.x before 1.36.3, and 1.37.x before 1.37.1. The WikibaseMediaInfo component is vulnerable to XSS via the caption fields for a given media file.
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 the WikibaseMediaInfo component of MediaWiki allows injection of malicious scripts through caption fields for media files. When users view affected media files, the unsanitized caption content executes in their browsers.
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< 1.35.5>= 1.36.0, < 1.36.3>= 1.37.0, < 1.37.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 MediaWiki installationLocate your MediaWiki installation directory or access Special:Version page on your wikiAffected if MediaWiki is present
-
Determine MediaWiki versionCheck the version in includes/Defines.php file or view Special:Version. Compare against affected ranges: < 1.35.5, >= 1.36.0 but < 1.36.3, >= 1.37.0 but < 1.37.1Affected if Installed version falls within any of these three ranges
-
Verify WikibaseMediaInfo extension is enabledCheck LocalSettings.php for 'WikibaseMediaInfo' inclusion or view Special:Version page to confirm the extension is listedAffected if WikibaseMediaInfo extension is installed and enabled
-
Check if caption editing is accessibleVerify users can access media file caption fields through the upload or media viewing interfaceAffected if Caption fields for media files are accessible to users
You are affected if your MediaWiki version is one of the vulnerable versions AND the WikibaseMediaInfo extension with caption functionality is enabled in your environment.
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 · scoped1.35.51.36.31.37.1
Update MediaWiki to version 1.35.5, 1.36.3, 1.37.1 or later to obtain the patch that properly sanitizes caption field input.
1.35.5, 1.36.3, or 1.37.1 (or later stable release)
- 1. Identify your current MediaWiki version by checking the $wgVersion variable in includes/DefaultSettings.php or the Special:Version page
- 2. Determine which upgrade path suits your current version: upgrade to 1.35.5+ if on 1.35.x, upgrade to 1.36.3+ if on 1.36.x, or upgrade to 1.37.1+ if on 1.37.x
- 3. Create a full backup of your MediaWiki database and files before proceeding
- 4. Download the appropriate fixed release from https://www.mediawiki.org/wiki/Download
- 5. Replace your existing MediaWiki files with the new version, preserving your LocalSettings.php and any custom configuration
- 6. Run the maintenance/update.php script to update the database schema if needed
- 7. Clear any caching systems (including PHP opcache and any CDN caches)
- 8. Verify the upgrade by checking Special:Version shows the correct version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46146 — 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-46146 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