dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-9192

HIGH · 8.8 CVSS v3.1 Published 2024-11-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 WordPress Video Robot - The Ultimate Video Importer plugin for WordPress is vulnerable to privilege escalation due to insufficient validation on user meta that can be updated in the wpvr_rate_request_result() function in all versions up to, and including, 1.20.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to update their user meta on a WordPress site. This can be leveraged to update their capabilities to that of an administrator.

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 WordPress Video Robot plugin up to version 1.20.0 contains a privilege escalation vulnerability in the wpvr_rate_request_result() function. Authenticated users with subscriber-level access can manipulate their user metadata to escalate privileges to administrator by exploiting insufficient validation on user meta updates.

MitigationUpdate the plugin to version 1.20.1 or later which contains proper capability validation. If immediate update is not possible, disable the plugin or restrict subscriber-level user registrations.

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 Video Robot plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Video Robot' or 'wpvr' in the plugin list. Note whether it is active or inactive.
    Affected if the plugin is installed and active with version 1.20.0 or earlier
  2. Confirm the installed plugin version
    Click on the plugin name in the Plugins list to view its details, or check the plugin's main PHP file header for the 'Version' constant. Compare this version to 1.20.0.
    Affected if the installed version is 1.20.0 or any earlier version of the Video Robot plugin
  3. Identify subscriber-level users
    In WordPress admin, go to Users > All Users and review the 'Role' column for any users assigned the 'Subscriber' role. Alternatively, use WP-CLI: wp user list --role=subscriber
    Affected if any user accounts with the Subscriber role exist in the WordPress installation
  4. Verify subscriber registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is enabled with 'New User Default Role' set to 'Subscriber'. Or inspect the site via REST API or check wp_options table for default_role.
    Affected if public registration is allowed and the default role is set to Subscriber
  5. Check if wpvr_rate_request_result is accessible
    Review the plugin's main PHP file (typically video-robot.php or similar) for the function wpvr_rate_request_result(). Verify if it is hooked to an action that can be accessed by authenticated users (check add_action calls).
    Affected if the function exists and is hooked to a publicly accessible action without capability checks

You are affected if the Video Robot plugin version 1.20.0 or earlier is active AND subscriber-level user accounts exist or can be registered on your site.

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 1.20.1 or later which contains proper capability validation. If immediate update is not possible, disable the plugin or restrict subscriber-level user registrations.

Recommended fix Moderate confidence

Latest version above 1.20.0

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Video Robot - The Ultimate Video Importer' plugin
  4. 4. Check if an update is available and update to the latest version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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