dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-62658

HIGH · 7.5 CVSS v4.0 Published 2025-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
Remotely reachable

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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in The Wikimedia Foundation MediaWiki WatchAnalytics extension allows SQL Injection.This issue affects MediaWiki WatchAnalytics extension: 1.43, 1.44.

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

SQL injection vulnerability in the MediaWiki WatchAnalytics extension allows attackers to inject malicious SQL commands through unsanitized input in database queries, potentially enabling unauthorized data access or modification.

MitigationFix requires identifying and rewriting vulnerable database queries to use parameterized queries or prepared statements instead of concatenating user input directly into SQL strings.

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
High
Privileges
Low
Authentication
Y
User interaction
P
Scope
N

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/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:N/AU:Y/R:U/V:C/RE:M/U:Amber

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. Confirm WatchAnalytics extension is installed
    Check your MediaWiki installation's extensions folder for the WatchAnalytics directory, and verify the extension is loaded in LocalSettings.php (look for 'wfLoadExtension( "WatchAnalytics" )' or similar)
    Affected if The WatchAnalytics extension directory exists and is enabled in MediaWiki configuration
  2. Identify WatchAnalytics version
    Check the extension's version file, composer.json, or extension.json in /extensions/WatchAnalytics/ for the installed version number
    Affected if The installed version is any version of WatchAnalytics (no version range was specified in the CVE)
  3. Locate vulnerable database query files
    Search the WatchAnalytics extension folder for PHP files that perform database queries, particularly in subdirectories like includes/, specials/, or api/. Look for files containing $dbr->query() or similar database function calls
    Affected if Database query files exist in the extension, as the vulnerability is in unsanitized SQL queries within these files
  4. Identify unsanitized user input in SQL queries
    Examine database query files for patterns where user-provided parameters (e.g., request parameters, form inputs, or user-supplied values) are concatenated directly into SQL strings without proper escaping or use of parameterized queries. Look for patterns like $sql = "SELECT..." . $userInput
    Affected if Code contains SQL queries where user input is concatenated directly into SQL strings without sanitization or prepared statements
  5. Verify affected API or special pages are accessible
    Identify if any Special pages or API modules provided by WatchAnalytics (such as Special:WatchAnalytics or related API endpoints) are accessible and accepting user input that flows into database queries
    Affected if WatchAnalytics special pages or API endpoints are accessible and process user-supplied parameters that reach the vulnerable database query code

Your environment is affected if the WatchAnalytics extension is installed and its code contains SQL queries that concatenate user input directly into SQL strings without parameterization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix requires identifying and rewriting vulnerable database queries to use parameterized queries or prepared statements instead of concatenating user input directly into SQL strings.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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