dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-62699

MEDIUM · 6.9 CVSS v4.0 Published 2025-10-21
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 - Translate Extension allows Footprinting. Translate extension appears to use jobs to make edits to translation pages. This causes the CheckUser tool to log the wrong IP and User-Agent making these edits un-auditable via the CheckUser tool.This issue affects Mediawiki - Translate Extension: from master before 1.39.

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 confidence

The Translate extension uses background jobs to make edits to translation pages, but fails to properly propagate user attribution context (IP address and User-Agent) to these background jobs. This causes the CheckUser tool to log the job runner's information instead of the actual editor's, making edit attribution un-auditable.

MitigationUpgrade Mediawiki Translate Extension to version 1.39 or later which properly propagates user attribution context to background jobs.

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:L/VA:L/SC:L/SI:L/SA:L/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. Locate the Translate extension version file
    Check the version.php file in the Translate extension directory (usually extensions/Translate/) for the $wgExtensionVersion variable or equivalent version constant
    Affected if The installed version is earlier than 1.39 (e.g., 1.38.x, 1.37.x, or older)
  2. Verify background job processing is enabled
    Check LocalSettings.php for $wgJobRunRate setting (typically set to a value > 0) or confirm that job runners are actively processing jobs via the MediaWiki job queue
    Affected if Background jobs are enabled ($wgJobRunRate > 0) and the Translate extension version is below 1.39
  3. Confirm Translate extension is actively used for translation workflows
    Check for recent translate* jobs in the job queue (e.g., translatejob, TranslateRenderJob) or review Special:TranslationStats if available
    Affected if The extension is actively processing translation-related background jobs on versions prior to 1.39

A user is affected if the Translate extension version is below 1.39 AND background job processing is enabled AND the Translate extension is actively used for translation workflows, causing edit attribution to show the job runner instead of the actual editor in CheckUser logs.

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 Translate Extension to version 1.39 or later which properly propagates user attribution context to background jobs.

Recommended fix Moderate confidence

Translate Extension version 1.39 or later (REL1_39 branch)

  1. 1. Identify the current version of the Translate extension in your MediaWiki installation by checking the 'extension.json' file in the Translate extension directory or running 'composer show wikimedia/mediawiki-translate'.
  2. 2. Navigate to your MediaWiki extensions directory and locate the Translate extension folder.
  3. 3. Backup your current Translate extension directory and any related configuration files.
  4. 4. Update the Translate extension to version 1.39 or later. If using Git, run: 'git fetch' followed by 'git checkout REL1_39' or fetch the specific tag for version 1.39. If using Composer, update via 'composer update wikimedia/mediawiki-translate'.
  5. 5. Clear any cached job queues to ensure new edits use the updated code with proper IP/User-Agent logging.
  6. 6. Verify the fix by making a test translation edit and confirming the CheckUser tool now correctly logs the originating IP and User-Agent for translation job edits.
Caveat No breaking changes are anticipated; this is a bug fix for logging behavior. Always test in a staging environment before deploying to production.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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