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

CVE-2025-31566

HIGH · 7.1 CVSS v3.1 Published 2025-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 riosisgroup Rio Video Gallery rio-video-gallery allows Stored XSS.This issue affects Rio Video Gallery: from n/a through <= 2.3.6.

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

CSRF vulnerability in the Rio Video Gallery WordPress plugin allows authenticated attackers to inject malicious JavaScript through Stored XSS by tricking administrators into unknowingly submitting crafted requests.

MitigationUpdate to the latest patched version of Rio Video Gallery and implement anti-CSRF tokens with proper input validation on all form submissions and AJAX 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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 Rio Video Gallery plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Rio Video Gallery' in the list, or check the /wp-content/plugins/ directory for the rio-video-gallery folder
    Affected if The plugin is not installed on the WordPress site
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Rio Video Gallery and view the version number displayed, or read the main plugin file header in /wp-content/plugins/rio-video-gallery/
    Affected if The version number is within the vulnerable range and has not been patched
  3. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify Rio Video Gallery shows as 'Active'
    Affected if The plugin is active and vulnerable version is running
  4. Inspect form submissions and AJAX actions for CSRF protection
    Use browser developer tools or a proxy to examine POST requests when adding/editing videos in the plugin. Check if the requests include a nonce token or CSRF token in the request body or headers
    Affected if Form submissions and AJAX actions lack CSRF token validation (no nonce or token present)
  5. Check for existing XSS payloads in the database
    Query the WordPress database tables where video data is stored (typically wp_posts or custom tables) for suspicious script tags or JavaScript event handlers in title, description, or URL fields related to the plugin
    Affected if Malicious JavaScript code is found stored in video metadata fields

You are affected if Rio Video Gallery plugin is installed, active, running a vulnerable unpatched version, and the plugin lacks CSRF protection on its forms or has stored XSS payloads in its data.

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

Update to the latest patched version of Rio Video Gallery and implement anti-CSRF tokens with proper input validation on all form submissions and AJAX actions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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