dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2001

HIGH · 8.8 CVSS v3.1 Published 2026-02-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The WowRevenue plugin for WordPress is vulnerable to unauthorized plugin installation due to a missing capability check in the 'Notice::install_activate_plugin' function in all versions up to, and including, 2.1.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to install arbitrary plugins on the affected site's server which may make remote code execution possible.

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 · high confidence

The WowRevenue WordPress plugin has a broken access control vulnerability in the Notice::install_activate_plugin function. The function lacks a capability check, allowing any authenticated user with subscriber-level privileges (the lowest WordPress role) to trigger arbitrary plugin installation on the server, which can lead to remote code execution.

MitigationUpdate the WowRevenue plugin to the latest version once available and add a capability check (e.g., manage_options) to the install_activate_plugin function. Review user accounts and installed plugins for any unauthorized changes.

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
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 WowRevenue plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WowRevenue' in the installed plugins list, or query the database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';
    Affected if WowRevenue plugin appears in the active plugins list
  2. Check for subscriber-level user accounts
    Go to Users > All Users in WordPress admin and review the role column, or query: SELECT user_login, user_email FROM wp_users WHERE ID IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%subscriber%');
    Affected if Any user accounts with Subscriber role exist on the site
  3. Verify plugin installation capability is not checked
    Review the WowRevenue plugin source code (if accessible via FTP or file manager) and search for the install_activate_plugin function to confirm it lacks a capability check for 'install_plugins' before execution
    Affected if The install_activate_plugin function executes without verifying the current user has install_plugins capability
  4. Audit recently installed or activated plugins
    Check the wp_options table for changes in active_plugins, or review server access logs for POST requests to /wp-admin/update.php or plugin installation endpoints
    Affected if New or unexpected plugins appear in active_plugins that were not intentionally installed by administrators
  5. Review user privilege changes
    Query user role assignments in wp_usermeta to detect any unauthorized role escalations, particularly to Administrator or Editor roles
    Affected if Users have been granted higher privileges than originally assigned

The site is affected if the WowRevenue plugin is installed and any subscriber-level user accounts exist, as the plugin allows low-privilege users to install and activate arbitrary plugins without authorization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WowRevenue plugin to the latest version once available and add a capability check (e.g., manage_options) to the install_activate_plugin function. Review user accounts and installed plugins for any unauthorized changes.

Recommended fix Moderate confidence

Any version of WowRevenue plugin greater than 2.1.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WowRevenue plugin
  4. If an update is available, click 'Update Now'
  5. Alternatively, download the latest version from the official WordPress plugin repository and upload/install it manually
  6. Verify the updated version is greater than 2.1.3

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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