Improper Privilege ManagementWeakness · CWE-269

CVE-2025-8899

HIGH · 8.8 CVSS v3.1 Published 2026-03-07
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 Paid Videochat Turnkey Site – HTML5 PPV Live Webcams plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 7.3.20. This is due to videowhisper_register_form() function not restricting user roles that can be set during registration. This makes it possible for authenticated attackers, with Author-level access and above, to create posts/pages with the registration form and administrator set as the role and subsequently use that form to register an administrator account. This can also be exploited by contributors, but is far less likely to be successful because an administrator would need to approve the form with the administrator role for the attack to be successful.

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 Paid Videochat Turnkey Site plugin for WordPress contains a privilege escalation vulnerability in the videowhisper_register_form() function. Authenticated users with Author-level access or higher can create pages/posts containing a registration form that allows specifying any role, including Administrator, enabling them to register new administrator accounts and escalate privileges.

MitigationUpdate the plugin to version 7.3.21 or later to patch the role restriction bypass. Review existing pages/posts containing the registration form for unauthorized administrator accounts and remove any suspicious newly-created admin accounts.

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 plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Paid Videochat Turnkey Site' (or VideoWhisper plugins). Note the installed version number.
    Affected if The plugin version is lower than 7.3.21 (the patched version).
  2. Identify registration form content
    Search your WordPress database or use the admin interface to find pages/posts containing the [videowhisper_register] shortcode or the videowhisper_register_form function call.
    Affected if Any pages or posts contain the registration form shortcode and are accessible to Author-level users.
  3. Audit administrator accounts
    Navigate to Users > All Users in WordPress admin. Review the list of users with Administrator role, focusing on account creation dates and any unfamiliar accounts.
    Affected if There are unexpected administrator accounts, especially created recently by users with Author access.
  4. Check user role assignment capabilities
    Review capabilities of users with Author role. Authors can typically create posts - verify if any Author-level users have created posts containing the registration form shortcode.
    Affected if Authors have created posts/pages containing the [videowhisper_register] shortcode.

You are affected if the plugin version is below 7.3.21 AND any Author-level user has created content with the registration form, or if unexpected administrator accounts exist in your users list.

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 plugin to version 7.3.21 or later to patch the role restriction bypass. Review existing pages/posts containing the registration form for unauthorized administrator accounts and remove any suspicious newly-created admin accounts.

Recommended fix Moderate confidence

7.3.21 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Paid Videochat Turnkey Site – HTML5 PPV Live Webcams' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the version number reflects the patched release (7.3.21 or higher)
  6. 6. Review user registrations to ensure no unauthorized administrator accounts were created

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8899 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8899 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