CVE-2026-40794
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 myCred <= 3.0.3 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 confidenceThis is a broken access control vulnerability in the myCred WordPress plugin (version 3.0.3 and below) that allows subscriber-level users to access functionality or data that should be restricted to higher-privileged roles. The CVSS 6.5 indicates network-exploitable with low attack complexity requiring some authentication, leading to limited confidentiality and integrity impact.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify myCred plugin is installed and activeLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'myCred' in the list. Alternatively, check the filesystem at /wp-content/plugins/ for a myCred folder and verify it contains the main plugin file.Affected if myCred plugin folder exists in /wp-content/plugins/ and the plugin is activated in WordPress admin
-
Identify installed myCred versionIn WordPress admin, go to Plugins > Installed Plugins and click on myCred to view the version number displayed in the plugin details. Alternatively, inspect the main plugin file header in /wp-content/plugins/mycred/plugin.php or mycred.php for the 'Version' comment tag.Affected if The displayed version number is 3.0.3 or lower (for example: 3.0.3, 3.0.2, 3.0.1, 2.x series, etc.)
-
Confirm presence of subscriber-level user accountsIn WordPress admin, navigate to Users > All Users. Review the 'Role' column to identify any users assigned the 'Subscriber' role. Alternatively, query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'.Affected if At least one user account exists with the Subscriber role assigned, providing a potential vector to exploit the broken access control
-
Check for sensitive myCred addon functionalityIn WordPress admin, go to myCred > Addons. Identify if any sensitive addons are enabled (examples: myCRED Transfer, myCred Point Logs, myCred Gateway modules). These represent the restricted functionality that subscriber-level users could potentially access in vulnerable versions.Affected if Sensitive addons or point management features are enabled, creating targets for unauthorized subscriber access
Your environment is affected if myCred plugin version 3.0.3 or below is installed and active with at least one subscriber-level user account present in WordPress.
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 dataUpgrade myCred to a version newer than 3.0.3 that contains the access control fix, or implement proper WordPress capability checks (current_user_can()) around sensitive functionality to enforce role-based access restrictions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40794 — 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-40794 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