Safeguard
Vulnerability Analysis•

CVE-2023-30873: Medium Access Control Flaw in WP Docs

CVE-2023-30873 is a Medium (CVSS 5.4) broken access control flaw in the WP Docs WordPress plugin up to 1.9.8. Update to version 1.9.9 or later.

Safeguard Security Team
3 min read

CVE-2023-30873 is a medium severity (CVSS 5.4) missing authorization flaw in the WP Docs WordPress plugin by Fahad Mahmood. It affects versions through 1.9.8, and the fix is to update to version 1.9.9 or later, as the Patchstack database entry for the plugin advises today.

What's affected

The NVD record says WP Docs is affected from n/a through 1.9.8. Patchstack's database entry, titled broken access control, lists the patched version as 1.9.9 and tells site owners to update to 1.9.9 or later. The record and Patchstack agree on the severity score of 5.4.

How to check if you're exposed

List the installed version with WP-CLI from the site root:

wp plugin list --name=wp-docs --fields=name,status,version

Or open Plugins in the WordPress admin and read the version under the plugin name. To update:

wp plugin update wp-docs

Safeguard's free in-browser scan at https://gold.safeguard.sh/scan checks dependency manifests, and it will not read a WordPress plugin list, so use WP-CLI or your hosting dashboard for this one.

What to do now

  1. Find every WordPress site that has the WP Docs plugin installed.
  2. Update the plugin to 1.9.9 or later.
  3. If you do not use the plugin, deactivate and delete it, which removes the exposure.
  4. Turn on auto updates for plugins you rely on, or review them on a fixed schedule.

Why it matters

The weakness is CWE-862, missing authorization. A function in the plugin does not check whether the person calling it has the right to do so. On a WordPress site that usually means a request that should need an editor or admin login can be made by a lower role or by a visitor, depending on the function.

Neither the record nor the Patchstack page we read says exactly which action is exposed, so avoid assuming more than the title says. The medium score reflects limited impact. Plugins with small user bases tend to get fixes late and unnoticed, which is why an inventory of installed plugins is the best early warning. The CVE is not on the CISA KEV list.

WordPress sites tend to collect plugins over time, and each one is code that runs with the site's database access. A plugin you installed for one project and forgot about still answers requests. Put the plugin list in an inventory, note the version, and review it when a CVE like this appears.

Also check whether the site has auto updates enabled for plugins. Patchstack notes that its users can turn on auto update for vulnerable plugins only, which is one way to apply security fixes quickly without taking every update automatically.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

What version fixes it?

Version 1.9.9 or later, according to Patchstack.

Does it need a login?

The sources do not say which role is required. Treat it as reachable by lower privileged users until you update.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.