CVE-2026-57661
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 · uneditedSubscriber Broken Access Control in WPComplete <= 2.9.5.5 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 confidenceBroken Access Control vulnerability in the WPComplete WordPress plugin allows authenticated users with Subscriber role to access functionality or data that should be restricted to higher-privileged roles. This indicates insufficient capability checks or authorization logic in the plugin's code, potentially letting low-privilege users perform actions intended for administrators or other privileged users.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WPComplete plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for WPComplete, or check the /wp-content/plugins/ directory for the wpcomplete folderAffected if WPComplete plugin is present on the WordPress site
-
Check installed WPComplete versionIn WordPress admin, go to Plugins > Installed Plugins and find WPComplete version number displayed under the plugin name, or inspect the main plugin file header for the Version fieldAffected if Version is 2.9.5.5 or earlier, or if the version cannot be determined and the plugin is installed
-
Confirm WordPress has Subscriber role enabledGo to Users > Users in WordPress admin and filter by role, or use a user role editor plugin or wp-cli command: wp user list --role=subscriberAffected if The Subscriber role exists and has at least one user account assigned to it
-
Verify if low-privilege users can access admin areasLog in as a user with Subscriber role and attempt to access wp-admin directly, or check if WPComplete exposes any admin URLs or AJAX endpoints accessible without proper capability checksAffected if Subscriber-level users can access pages or functionality intended only for administrators or higher roles
If WPComplete version 2.9.5.5 or earlier is installed AND the site has Subscriber role users, the environment is likely affected by this broken access control vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate WPComplete to a version newer than 2.9.5.5 which contains proper access control enforcement, or implement plugin-level capability checks on all sensitive functions until the vendor patch is applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-57661 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57661 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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