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

CVE-2025-60132

HIGH · 7.1 CVSS v3.1 Published 2025-10-22
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 johnh10 Video Blogster Lite video-blogster-lite allows Stored XSS.This issue affects Video Blogster Lite: from n/a through <= 1.2.

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

A CSRF vulnerability in Video Blogster Lite enables attackers to trick authenticated administrators into unknowingly submitting malicious requests that store XSS payloads in the plugin's database. When other users view the affected video content pages, the stored JavaScript executes in their browsers, potentially leading to session hijacking or further privilege escalation.

MitigationImplement anti-CSRF tokens on all state-changing forms and validate request origin/referer headers; sanitize and escape all user-supplied content before storing and rendering.

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. Confirm Video Blogster Lite plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Video Blogster Lite'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'video-blogster-lite' or similar.
    Affected if The plugin is installed and active, exposing the CSRF-to-stored-XSS attack surface.
  2. Identify the installed version
    In WordPress admin Plugins page, find Video Blogster Lite and read the version number displayed under the plugin name. Compare this version to any known affected version ranges if publicly disclosed.
    Affected if The installed version falls within the affected version range for this CVE.
  3. Inspect database for stored XSS payloads
    Query the WordPress database tables (typically wp_options, wp_posts, or any custom tables created by the plugin) for suspicious script tags, JavaScript event handlers, or encoded payloads. Use: SELECT * FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onerror=%' OR post_content LIKE '%onload=%';
    Affected if Any video entries, settings, or content fields contain unsanitized script tags or event handlers that could execute.
  4. Check admin configuration forms for CSRF protection
    View the source code of Video Blogster Lite admin pages (settings, video import, or content management forms). Look for hidden CSRF token fields (typically named 'nonce', '_wpnonce', or 'csrf_token') in the HTML forms.
    Affected if State-changing admin forms (save settings, add/edit videos) lack CSRF token fields or token validation.
  5. Examine video content pages for XSS execution
    Visit the frontend pages where video content is displayed (blog posts, video archive pages). View the page source and check if user-supplied title, description, or embed fields are rendered with proper encoding (e.g., &lt;script&gt; should appear as HTML entities, not raw tags).
    Affected if Content entered through the plugin admin is rendered without HTML escaping on the frontend.

A user is affected if Video Blogster Lite is active, the version is within the affected range, and the database contains unsanitized XSS payloads or the admin forms lack CSRF protection.

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 on all state-changing forms and validate request origin/referer headers; sanitize and escape all user-supplied content before storing and rendering.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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