FedoraOperating system · Fedoraproject
CVE-2020-25813
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, Special:UserRights exposes the existence of hidden users.
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 confidenceIn MediaWiki versions prior to 1.31.10 and 1.32.x through 1.34.x before 1.34.4, the Special:UserRights page reveals whether hidden user accounts exist in the system. This information disclosure allows attackers to enumerate valid usernames by attempting to modify rights on non-existent versus existing hidden accounts.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 versionOpen includes/DefaultSettings.php and locate the $wgVersion variable, or access Special:Version on your wikiAffected if Version is less than 1.31.10, or between 1.32.0 and 1.34.3 inclusive
-
Identify if hidden users are configuredCheck your LocalSettings.php for $wgHiddenUsers array or review special user groups with hidden attributes using a database query on the user tableAffected if Any hidden user accounts exist in the system (non-empty $wgHiddenUsers or hidden user groups)
-
Determine who can access Special:UserRightsReview user group permissions in LocalSettings.php, specifically check if users other than administrators can access the 'userrights' right via $wgGroupPermissionsAffected if Non-admin users or anonymous users have permission to access Special:UserRights (userrights right)
-
Verify the information disclosure existsAs a low-privilege user with userrights access, attempt to modify rights for a known hidden username via Special:UserRights and observe whether the response differs between existing hidden users versus non-existent accountsAffected if The page response differs between existing hidden users and non-existent usernames, revealing account existence
You are affected if your MediaWiki version falls in the vulnerable range AND you have hidden users configured AND low-privilege users can access Special:UserRights.
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 patch the information disclosure vulnerability in Special:UserRights.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25813 — 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-25813 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