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

CVE-2025-7812

HIGH · 8.8 CVSS v3.1 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
The Video Share VOD – Turnkey Video Site Builder Script plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.7.6. This is due to missing or incorrect nonce validation on the adminExport() function. This makes it possible for unauthenticated attackers to update settings and execute remote code when the Server command execution setting is enabled via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Video Share VOD WordPress plugin versions up to 2.7.6 lacks proper nonce validation in its adminExport() function, allowing unauthenticated attackers to forge administrative requests. When the 'Server command execution' setting is enabled, a successful CSRF attack can trigger remote code execution on the server by tricking an administrator into clicking a malicious link.

MitigationUpdate to version 2.7.7 or later which implements proper nonce validation; until then, disable the Server command execution setting and warn administrators against clicking untrusted links.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Share VOD plugin is installed
    Check the WordPress plugins directory or admin panel for the Video Share VOD plugin presence
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    View the plugin version in the WordPress plugin admin page or inspect the plugin's main PHP file for the Version header
    Affected if Installed version is 2.7.6 or lower (any version up to and including 2.7.6)
  3. Locate the Server command execution setting
    Navigate to the plugin settings in WordPress admin panel and look for a setting labeled 'Server command execution' or similar
    Affected if This setting exists and is currently enabled (checked/active)
  4. Verify the adminExport function is accessible
    Inspect the plugin source code for the adminExport() function and confirm it lacks nonce validation checks (look for wp_verify_nonce or check_admin_referer calls)
    Affected if The function exists without proper nonce validation

A user is affected if the Video Share VOD plugin version is 2.7.6 or lower AND the Server command execution setting is enabled, making the CSRF-to-RCE attack vector viable.

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 to version 2.7.7 or later which implements proper nonce validation; until then, disable the Server command execution setting and warn administrators against clicking untrusted links.

Recommended fix Moderate confidence

Latest version after 2.7.6 (check wordpress.org/plugins for current stable release)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Video Share VOD – Turnkey Video Site Builder Script' plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. If no update is available through WordPress, manually download the latest version from wordpress.org/plugins and upload it
  6. 6. After updating, verify the 'Server command execution' setting in plugin settings and disable it if enabled (this setting allows remote code execution and should not be enabled)
  7. 7. Confirm the nonce validation fix is applied by reviewing the adminExport() function code if possible

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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