dbcve.org
Debian LinuxOperating system · Debian

CVE-2019-12470

MEDIUM · 6.5 CVSS v3.0 Published 2019-07-10
Fix available
A fix is available. Upgrade to 1.27.6 / 1.30.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Wikimedia MediaWiki through 1.32.1 has Incorrect Access Control. Suppressed log in RevisionDelete page is 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 · high confidence

MediaWiki versions through 1.32.1 contain an incorrect access control vulnerability in the RevisionDelete feature. A suppressed log entry (hidden revision information that should only be visible to privileged users) was being exposed to unauthorized users through the RevisionDelete page interface.

MitigationApply the MediaWiki security patches by upgrading to version 1.32.2, 1.31.2, 1.30.2, or 1.27.6 or later, as these versions contain the access control fix for the exposed suppressed log.

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
Affected:= 9.0
MediawikiCMS
Affected:< 1.27.6>= 1.27.7, < 1.30.2>= 1.31.0, < 1.31.2>= 1.32.0, < 1.32.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MediaWiki version
    Locate the file 'includes/Defines.php' or 'composer.json' in your MediaWiki installation directory and look for the $wgVersion variable or version entry. Alternatively, access /api.php?action=query&meta=siteinfo&format=json and look for the 'version' field in the response.
    Affected if The installed version falls within < 1.27.6, >= 1.27.7 and < 1.30.2, >= 1.31.0 and < 1.31.2, or >= 1.32.0 and < 1.32.2.
  2. Verify RevisionDelete module is accessible
    Check if the 'revisiondelete' user right is assigned to any user group in your MediaWiki by examining LocalSettings.php for $wgGroupPermissions configuration or checking Special:Version in the web interface for the RevisionDelete extension.
    Affected if Users without sufficient privileges (such as anonymous users or regular users not in the 'suppressor' or 'sysop' groups with specific rights) can access the RevisionDelete interface.
  3. Identify suppressed log entries in the system
    Query the database table 'logging' where 'log_deleted' field contains bitmask values indicating suppression (typically non-zero values), or access Special:Log/delete to view suppressed entries if you have proper rights.
    Affected if Suppressed log entries exist in the database and the system allows unauthorized access to view them through the RevisionDelete interface.
  4. Test unauthorized access to suppressed content
    As a non-privileged user (or anonymous), navigate to Special:RevisionDelete and attempt to view any revision or log entry that has been suppressed. Check if suppressed revisions become visible without proper authentication as a user with 'suppressrevision' right.
    Affected if Suppressed or hidden revisions are displayed to users lacking the 'suppressrevision' or 'viewsuppressed' permissions.

Your environment is affected if you run a MediaWiki version within the affected ranges AND have the RevisionDelete feature accessible to users who should not have visibility into suppressed log entries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.27.6 / 1.30.2 / 1.31.2 or later
Fixed in 1.27.61.30.21.31.2
Interim mitigation

Apply the MediaWiki security patches by upgrading to version 1.32.2, 1.31.2, 1.30.2, or 1.27.6 or later, as these versions contain the access control fix for the exposed suppressed log.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-12470 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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