dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-57886

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Authorization Bypass Through User-Controlled Key vulnerability in Equalize Digital Accessibility Checker by Equalize Digital accessibility-checker allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Accessibility Checker by Equalize Digital: from n/a through <= 1.30.0.

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 Accessibility Checker plugin by Equalize Digital versions up to 1.30.0 contain an authorization bypass vulnerability where user-controlled keys allow attackers to exploit incorrectly configured access control security levels, enabling unauthorized access to functionality or data that should be restricted.

MitigationUpdate the Accessibility Checker plugin to a version beyond 1.30.0, or apply vendor-supplied security patches to fix the incorrectly configured access control security levels.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 Accessibility Checker plugin version
    Access your WordPress site via FTP or file manager, navigate to wp-content/plugins/equalize-accessibility-checker/ folder, and open the main plugin file (typically equalize-accessibility-checker.php) or the readme.txt file to find the Version: entry
    Affected if The version listed is 1.30.0 or lower
  2. Confirm the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or check the wp_options table in the database for the active_plugins option to see if equalize-accessibility-checker is enabled
    Affected if The plugin is active and the version is 1.30.0 or lower
  3. Inspect plugin access control configuration
    Examine the plugin files for settings or functions that handle user-supplied keys, tokens, or identifiers used in authorization checks. Look in includes/ or classes/ directories for access control, capability checks, or permission-related code
    Affected if The plugin contains functionality where user-controlled keys or parameters influence access control decisions without proper validation

Your environment is affected if the Accessibility Checker plugin version is 1.30.0 or lower and the plugin is active, with user-controlled keys or parameters being used in access control logic.

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

Update the Accessibility Checker plugin to a version beyond 1.30.0, or apply vendor-supplied security patches to fix the incorrectly configured access control security levels.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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