CVE-2025-0955
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 · uneditedThe VidoRev Extensions plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the 'vidorev_import_single_video' AJAX action in all versions up to, and including, 2.9.9.9.9.9.5. This makes it possible for unauthenticated attackers to import arbitrary youtube videos.
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 confidenceThe VidoRev WordPress plugin has a missing capability check on the 'vidorev_import_single_video' AJAX action, allowing unauthenticated attackers to invoke this function and import arbitrary YouTube videos into the site. This is a broken access control (CWE-862) vulnerability rated CVSS 5.3.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm VidoRev plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'VidoRev' in the list. Alternatively, check for the presence of the plugin directory at /wp-content/plugins/vidorev-theme-extensions/ or similar.Affected if VidoRev plugin is found in the WordPress installation
-
Identify the installed VidoRev versionIn WordPress admin, click on the VidoRev plugin in the plugin list to view its version number. Alternatively, check the plugin's main PHP file for a version constant or header.Affected if The installed version matches or falls within the affected version range (if known)
-
Verify the vulnerable AJAX action is registeredExamine the plugin source code for the registration of 'vidorev_import_single_video' AJAX action using add_action('wp_ajax_vidorev_import_single_video', ...) and verify if it includes a nopriv variant (wp_ajax_nopriv_vidorev_import_single_video).Affected if The AJAX action is registered without a corresponding capability check and is accessible to unauthenticated users
-
Inspect the callback function for capability checksLocate the callback function handling 'vidorev_import_single_video' and search for current_user_can() or similar authorization checks within the function.Affected if No capability check (such as current_user_can('manage_options')) is found inside the callback function
A user is affected if VidoRev plugin is installed and the vidorev_import_single_video AJAX action is accessible without authentication due to missing capability checks.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply a capability check (e.g., current_user_can('manage_options')) to the vidorev_import_single_video AJAX action, or update to a patched version when released by the vendor.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0955 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0955 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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