dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-30986

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in _CreativeMedia_ Elite Video Player elite-video-player allows Cross Site Request Forgery.This issue affects Elite Video Player: from n/a through <= 10.0.5.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Elite Video Player WordPress plugin (versions up to and including 10.0.5) allows attackers to trick authenticated administrators into performing unintended actions via maliciously crafted requests.

MitigationImplement anti-CSRF tokens (nonce validation) on all state-changing operations (settings updates, configuration changes, video management actions) within the plugin, and ensure the WordPress nonces are properly validated on any admin-side actions.

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

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 Elite Video Player plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or use WP-CLI: wp plugin list --name='elite-video-player' --status=active
    Affected if Plugin is not installed or not active - not affected. If installed and active, continue to version check.
  2. Determine installed plugin version
    In WordPress admin, find Elite Video Player in the plugins list and note the version number displayed. Alternatively, check the main plugin file header at wp-content/plugins/elite-video-player/ for the 'Version' comment tag.
    Affected if Version is 10.0.5 or lower - vulnerable to CVE-2025-30986. Versions above 10.0.5 may include the fix.
  3. Identify admin action endpoints lacking nonce validation
    Review plugin source code in wp-content/plugins/elite-video-player/ for admin action handlers (look for 'admin_init', 'add_action' calls handling form submissions) and check if each handler calls wp_verify_nonce() or check_admin_referer() before processing state-changing requests.
    Affected if Any admin action handler processes request data (settings updates, video management, configuration changes) without first validating a nonce - vulnerable to CSRF.

You are affected if the Elite Video Player plugin is active at version 10.0.5 or lower AND any administrative state-changing operations lack WordPress nonce validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonce validation) on all state-changing operations (settings updates, configuration changes, video management actions) within the plugin, and ensure the WordPress nonces are properly validated on any admin-side actions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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