dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-53495

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Wikimedia Foundation Mediawiki - AbuseFilter Extension allows Unauthorized Access.This issue affects Mediawiki - AbuseFilter Extension: from 1.43.X before 1.43.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 · moderate confidence

Missing authorization check in MediaWiki's AbuseFilter extension allows unauthenticated or unauthorized users to access functionality they should not have permission to use. This is a classic authorization bypass vulnerability in the extension affecting versions 1.43.x before 1.43.2, rated critical at CVSS 9.1.

MitigationUpgrade MediaWiki AbuseFilter extension to version 1.43.2 or later to receive the authorization fix. Review user permissions and audit access logs for any exploitation attempts.

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm MediaWiki installation and version
    Locate the MediaWiki installation directory and check the version in includes/Defines.php or includes/Setup.php for the MW_VERSION constant, or look for a version file in the root directory.
    Affected if MediaWiki version is 1.43.x (any patch version below 1.43.2)
  2. Locate the AbuseFilter extension
    Check if the extensions/AbuseFilter/ directory exists in your MediaWiki installation.
    Affected if The AbuseFilter extension directory is present in the installation
  3. Determine AbuseFilter extension version
    Check the extension version file or extension.json in extensions/AbuseFilter/ - the version may be listed in a VERSION file, composer.json, or the extension.json manifest.
    Affected if AbuseFilter extension version is 1.43.0 or 1.43.1 (any version before 1.43.2)
  4. Verify AbuseFilter is enabled
    Check your LocalSettings.php for a line like 'wfLoadExtension( "AbuseFilter" );' or similar require/include statements that enable the AbuseFilter extension.
    Affected if The AbuseFilter extension is enabled in the MediaWiki configuration
  5. Review user permissions configuration
    Check the $wgGroupPermissions array in LocalSettings.php for any AbuseFilter-related permission settings, and examine if unauthenticated or low-privilege users have access to AbuseFilter tools.
    Affected if Users without proper authorization (such as anonymous users or low-privilege accounts) have been granted access to AbuseFilter functionality

You are affected if MediaWiki with the AbuseFilter extension is installed and the AbuseFilter version is 1.43.0 or 1.43.1 (any version before 1.43.2), and the extension is enabled.

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 AbuseFilter extension to version 1.43.2 or later to receive the authorization fix. Review user permissions and audit access logs for any exploitation attempts.

Recommended fix High confidence

MediaWiki AbuseFilter Extension 1.43.2

  1. Identify the current version of MediaWiki and the AbuseFilter extension by checking the installed version or the Special:Version page
  2. Backup the MediaWiki database and configuration files before performing any upgrade
  3. Update the AbuseFilter extension to version 1.43.2 using the appropriate method (composer update or extension-specific update mechanism)
  4. Run any required database updates (php maintenance/update.php or equivalent)
  5. Clear MediaWiki caches to ensure the new version is fully active
  6. Verify the upgrade was successful by checking the version on Special:Version and confirming the AbuseFilter extension shows version 1.43.2 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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