dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-47848

MEDIUM · 6.9 CVSS v4.0 Published 2024-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in The Wikimedia Foundation Mediawiki - PageTriage allows Authentication Bypass.This issue affects Mediawiki - PageTriage: from 1.39.X before 1.39.9, from 1.41.X before 1.41.3, from 1.42.X before 1.42.2.

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

The PageTriage extension in MediaWiki versions 1.39.x before 1.39.9, 1.41.x before 1.41.3, and 1.42.x before 1.42.2 contains an authentication bypass vulnerability that allows unauthorized actors to access sensitive information without proper authentication credentials.

MitigationUpgrade MediaWiki to version 1.39.9, 1.41.3, 1.42.2 or later to patch the authentication bypass in the PageTriage extension. Verify the update in a staging environment before production deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify PageTriage extension is installed
    Check your MediaWiki configuration (LocalSettings.php or the extensions/PageTriage directory) for the PageTriage extension. If the extension directory exists and the extension is loaded in your configuration, it is present.
    Affected if PageTriage extension is installed and enabled in MediaWiki
  2. Determine the installed MediaWiki version
    Access the MediaWiki API at /api.php?action=query&meta=siteinfo&format=json and look for the 'version' field, or check the includes/Version.php file in your MediaWiki installation.
    Affected if Unable to determine the version through standard MediaWiki methods
  3. Compare against vulnerable version 1.39.x
    If running MediaWiki 1.39.x, check if the version is below 1.39.9 (e.g., 1.39.0 to 1.39.8 are vulnerable).
    Affected if MediaWiki version is 1.39.x and is earlier than 1.39.9
  4. Compare against vulnerable version 1.41.x
    If running MediaWiki 1.41.x, check if the version is below 1.41.3 (e.g., 1.41.0 to 1.41.2 are vulnerable).
    Affected if MediaWiki version is 1.41.x and is earlier than 1.41.3
  5. Compare against vulnerable version 1.42.x
    If running MediaWiki 1.42.x, check if the version is below 1.42.2 (e.g., 1.42.0 to 1.42.1 are vulnerable).
    Affected if MediaWiki version is 1.42.x and is earlier than 1.42.2

You are affected if the PageTriage extension is installed and your MediaWiki version falls within 1.39.x before 1.39.9, 1.41.x before 1.41.3, or 1.42.x before 1.42.2.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MediaWiki to version 1.39.9, 1.41.3, 1.42.2 or later to patch the authentication bypass in the PageTriage extension. Verify the update in a staging environment before production deployment.

Recommended fix High confidence

Upgrade to MediaWiki 1.39.9+, 1.41.3+, or 1.42.2+ depending on your current branch

  1. Identify the currently installed MediaWiki PageTriage version using your system's package manager or MediaWiki's Special:Version page
  2. For MediaWiki 1.39.x installations: upgrade to version 1.39.9 or later
  3. For MediaWiki 1.41.x installations: upgrade to version 1.41.3 or later
  4. For MediaWiki 1.42.x installations: upgrade to version 1.42.2 or later
  5. After upgrading, verify the fix by confirming the new version number in Special:Version and testing PageTriage functionality
  6. Review any related security advisories on gerrit.wikimedia.org for additional context
Caveat MediaWiki minor version updates typically do not introduce breaking changes; always review the release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47848 — 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-2024-47848 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