Debian LinuxOperating system · Debian
CVE-2019-12469
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 · uneditedMediaWiki through 1.32.1 has Incorrect Access Control. Suppressed username or log in Special:EditTags are exposed. Fixed in 1.32.2, 1.31.2, 1.30.2 and 1.27.6.
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 confidenceMediaWiki through 1.32.1 has an Incorrect Access Control vulnerability where suppressed (hidden) usernames or edit logs are exposed in the Special:EditTags page. This allows unauthorized users to view information that should be hidden due to privacy or administrative policies.
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
Debian LinuxOperating system
= 9.0< 1.27.6>= 1.27.7, < 1.30.2>= 1.31.0, < 1.31.2>= 1.32.0, < 1.32.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 versionNavigate to Special:Version on your wiki or check the includes/Defines.php file for the MW_VERSION constantAffected if The installed version is < 1.27.6, or >= 1.27.7 and < 1.30.2, or >= 1.31.0 and < 1.31.2, or >= 1.32.0 and < 1.32.2
-
Verify if suppressed users or edit logs existCheck your database for entries in the revision table with rev_deleted = 1 or in the logging table with log_deleted = 1, or check Special:Log/delete for suppressed entriesAffected if There are suppressed (hidden) usernames or edit log entries in your wiki database
-
Test access to Special:EditTags as a low-privilege userLog in with a user account that does not have the suppressrevision or hideuser right and navigate to Special:EditTagsAffected if A non-privileged user can view usernames or log entries that are marked as suppressed
-
Query database for visible suppressed dataRun a query joining revision and logging tables where rev_deleted or log_deleted bits are set, and verify if those records are accessible via Special:EditTagsAffected if Suppressed records are returned or displayed to users lacking suppress rights
You are affected if your MediaWiki version falls within the vulnerable ranges AND you have suppressed users or edit logs that are visible to unauthorized users through Special:EditTags.
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.27.61.30.21.31.2
Upgrade MediaWiki to version 1.32.2, 1.31.2, 1.30.2, or 1.27.6 or later to apply the access control fix.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12469 — 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-2019-12469 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