dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57654

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

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
Affiliate Broken Access Control in Affiliates Manager <= 2.9.49 versions.

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

Broken access control vulnerability in the Affiliates Manager plugin for WordPress allows unauthorized users to access affiliate management functions due to missing or improper authorization checks in versions 2.9.49 and below.

MitigationUpdate Affiliates Manager plugin to the latest version (>2.9.49) and verify that proper role-based access controls are enforced for all affiliate management 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Verify Affiliates Manager plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the affiliates-manager or similar Affiliates Manager plugin folder, or list installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically the primary file in the plugin folder, often named affiliates-manager.php or similar) and locate the version defined in the plugin header comment (look for 'Version: x.x.x')
    Affected if The version number returned is 2.9.49 or lower
  3. Compare version against the vulnerable range
    Compare the identified version number to the affected range: if the version is 2.9.49 or below (e.g., 2.9.48, 2.9.40, etc.), the installation falls within the vulnerable range
    Affected if The installed version is 2.9.49 or any version lower than 2.9.49
  4. Confirm plugin is active
    Check WordPress admin under Plugins > Installed Plugins to verify whether the Affiliates Manager plugin is currently activated
    Affected if The plugin is both installed at a vulnerable version AND currently activated

A user is affected if the Affiliates Manager WordPress plugin is installed, active, and running at version 2.9.49 or below.

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

Update Affiliates Manager plugin to the latest version (>2.9.49) and verify that proper role-based access controls are enforced for all affiliate management operations.

Recommended fix Moderate confidence

Latest version of Affiliates Manager (version 2.9.50 or higher)

  1. 1. Back up your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the 'Affiliates Manager' plugin in the list.
  4. 4. Check if the current installed version is 2.9.49 or earlier.
  5. 5. If vulnerable, click 'Update Now' to install the latest available version, or manually download the updated plugin from a trusted source if auto-update is not available.
  6. 6. After updating, verify the plugin is functioning correctly on your site.
  7. 7. Test that affiliate management functionality (adding/editing/deleting affiliates) works as expected and that unauthorized access is now properly restricted.

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

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-2026-57654 — 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-2026-57654 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