dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-62666

MEDIUM · 6.9 CVSS v4.0 Published 2025-10-18
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
Allocation of Resources Without Limits or Throttling vulnerability in The Wikimedia Foundation Mediawiki - CirrusSearch Extension allows HTTP DoS.This issue affects Mediawiki - CirrusSearch Extension: from master before 1.43.

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 CirrusSearch extension in MediaWiki versions before 1.43 lacks proper resource limits or throttling on search queries, allowing attackers to craft expensive search requests that consume excessive server resources and cause HTTP-based denial of service.

MitigationImplement query complexity limits and request throttling in the CirrusSearch configuration to restrict resource-intensive search operations.

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. Check MediaWiki version
    Locate the version file (e.g., includes/DefaultSettings.php or composer.json) or access /api.php?action=query&meta=siteinfo&format=json to retrieve the installed MediaWiki version number
    Affected if The installed version is earlier than 1.43 (e.g., 1.42.x, 1.41.x, etc.)
  2. Verify CirrusSearch extension is enabled
    Check LocalSettings.php for the line 'wfLoadExtension( 'CirrusSearch' );' or inspect the extension.json file in the CirrusSearch directory
    Affected if CirrusSearch is loaded and active in the MediaWiki installation
  3. Confirm no query complexity limits are configured
    Examine LocalSettings.php and any CirrusSearch configuration files (e.g., config.yaml or CirrusSearch-related $wgCirrusSearch* variables) for settings such as $wgCirrusSearchMaxClauseCount, $wgCirrusSearchSearchType, or similar query throttling parameters
    Affected if No resource limit or query complexity settings are defined for CirrusSearch, leaving search queries unrestricted

The environment is affected if MediaWiki version is before 1.43, CirrusSearch is enabled, and no query complexity or throttling limits are configured in the CirrusSearch settings.

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

Implement query complexity limits and request throttling in the CirrusSearch configuration to restrict resource-intensive search operations.

Recommended fix Moderate confidence

1.43

  1. 1. Back up your MediaWiki installation and database before proceeding with any upgrade.
  2. 2. Navigate to your MediaWiki extensions directory (usually /extensions/CirrusSearch).
  3. 3. Update the CirrusSearch extension to version 1.43 or later using your preferred method (e.g., git pull, Composer, or downloading the release).
  4. 4. Run the MediaWiki update script (php maintenance/update.php) to apply any database schema changes required by the new version.
  5. 5. Clear any relevant caches (e.g., job queue, search index caches) to ensure the new code is active.
  6. 6. Verify the CirrusSearch extension is running the updated version by checking the Special:Version page in your MediaWiki installation.
  7. 7. Test search functionality to confirm normal operation.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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