dbcve.org
Wp DocsWordPress extension · Androidbubble

CVE-2023-30873

HIGH · 8.8 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 1.9.9 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Fahad Mahmood WP Docs allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Docs: from n/a through 1.9.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 confidence

Missing Authorization vulnerability in the WP Docs WordPress plugin allows unauthenticated or insufficiently authenticated users to access sensitive functionality due to incorrectly configured access control security levels. The plugin fails to properly validate user capabilities before performing privileged operations.

MitigationAdd proper capability checks and nonce verification to all sensitive functions in the plugin, ensuring only users with appropriate permissions can access documented functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp DocsWordPress extension
Affected:< 1.9.9

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
High
Integrity
High
Availability
High

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

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 WP Docs plugin is installed
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WP Docs' or 'Androidbubble Wp Docs' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list, regardless of activation status.
  2. Determine installed version number
    In the Plugins list, click on the plugin name to view details, or check the plugin header in /wp-content/plugins/wp-docs/ folder for the Version field.
    Affected if The version number displayed is less than 1.9.9 (for example, 1.9.8, 1.9.7, 1.0.0, etc.).
  3. Inspect plugin file for capability checks
    Examine the main plugin PHP file (typically wp-docs.php or similar in the wp-docs folder) and look for function declarations that perform sensitive operations. Check if these functions include current_user_can() or similar WordPress capability verification before executing privileged actions.
    Affected if Sensitive functions lack proper current_user_can() checks or capability validation at the function entry point.
  4. Test unauthenticated access to plugin functions
    Attempt to access plugin-related URLs or AJAX endpoints (commonly /wp-admin/admin-ajax.php with plugin-specific actions) without logging in or with a low-privilege user account. Compare behavior against a properly authorized admin user.
    Affected if Unauthenticated users or subscribers/contributors can perform actions that should require administrator-level permissions.

Your environment is affected if the WP Docs plugin is installed with a version lower than 1.9.9 AND the plugin allows unauthenticated or low-privilege users to access administrative functionality.

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
Upgrade available Upgrade to 1.9.9 or later
Fixed in 1.9.9
Interim mitigation

Add proper capability checks and nonce verification to all sensitive functions in the plugin, ensuring only users with appropriate permissions can access documented functionality.

Recommended fix High confidence

WP Docs version 1.9.9

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP Docs plugin in the list
  4. If an update is available, click 'Update Now' to upgrade to version 1.9.9 or later
  5. Alternatively, go to Plugins > Add New > Upload Plugin and upload the latest version from WordPress.org
  6. Verify the plugin version shows 1.9.9 or higher after updating
  7. Test that the authorization controls are functioning correctly after the update

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

Fix this in Wp Docs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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