CVE-2026-24990
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 · uneditedMissing Authorization vulnerability in Fahad Mahmood WP Docs wp-docs allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Docs: from n/a through <= 2.2.8.
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 confidenceThe WP Docs plugin has a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This broken access control issue likely enables lower-privileged users or unauthenticated actors to access functionality or data they should not be permitted to reach.
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.
-
Identify if WP Docs plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or use WP-CLI: wp plugin list --name='wp-docs' or search for 'wp-docs' in plugins directoryAffected if WP Docs plugin is active on the WordPress site
-
Determine installed WP Docs versionCheck plugin version in plugin header comment at wp-content/plugins/wp-docs/*.php, or view plugin details in WordPress admin plugins listAffected if Version is unpatched and falls within vulnerable version range (compare against any published security advisory)
-
Inspect user role and capability assignmentsGo to WordPress admin > Users > Roles, or query wp_options for roles/capabilities, or use a user role editor plugin to review what capabilities are assigned to subscriber/contributor/author rolesAffected if Lower-privileged users (subscribers, contributors) have elevated capabilities they should not possess
-
Test access to privileged plugin functionsAs a low-privileged user (subscriber level), attempt to access WP Docs admin pages, create/edit documents, or modify plugin settings via direct URL access or API endpointsAffected if Low-privileged users can access admin pages, create/edit documents, or modify settings they should not be able to reach
-
Verify authorization on sensitive plugin actionsUse browser developer tools or a request interceptor to examine non-authenticated or low-privilege requests to plugin AJAX actions (wp-admin/admin-ajax.php) or REST API endpoints related to WP DocsAffected if Sensitive actions respond successfully without proper capability verification
The environment is affected if the WP Docs plugin is installed and running, and low-privileged or unauthenticated users can access functionality or data that requires higher-level permissions.
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 dataImplement proper capability checks and authorization verification on all sensitive functions and data access points within the plugin, ensuring user permissions are validated before executing any privileged operations.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24990 — 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-24990 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