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

CVE-2025-30769

HIGH · 7.1 CVSS v3.1 Published 2025-03-27
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 alexvtn WIP WooCarousel Lite wip-woocarousel-lite allows Stored XSS.This issue affects WIP WooCarousel Lite: from n/a through <= 1.1.7.

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 WIP WooCarousel Lite WordPress plugin allows authenticated attackers to inject malicious JavaScript through admin actions, resulting in Stored XSS. The lack of anti-CSRF token validation on plugin settings/endpoints enables attackers to craft malicious requests that execute in the browsers of users viewing carousel content.

MitigationImplement nonces/tokens for all state-changing admin actions and apply proper input sanitization and output encoding to prevent XSS. Users should update to the latest patched version when available.

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 WooCarousel Lite plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WIP WooCarousel Lite' or check the /wp-content/plugins/woocarousel-lite directory exists
    Affected if The plugin is installed and active
  2. Identify the installed version
    In WordPress admin Plugins page, find WooCarousel Lite and note the version number displayed, or check the main plugin PHP file header for 'Version:' tag
    Affected if Version cannot be determined or is older than the patched version (compare to latest available version on WordPress.org)
  3. Inspect plugin admin nonce implementation
    Examine the main plugin PHP file (e.g., woocarousel-lite.php) for admin action handlers and check if they validate nonces using functions like wp_verify_nonce or check_admin_referer
    Affected if Admin settings actions lack nonce/token validation (no wp_verify_nonce, check_admin_referer, or similar CSRF protection found)
  4. Check plugin settings for suspicious stored content
    Access the plugin settings pages in WordPress admin (WooCarousel menu) and inspect all text fields for any unexpected JavaScript:alert, script tags, or encoded payloads
    Affected if Any settings fields contain unexpected script tags, event handlers, or encoded JavaScript that was not entered by an authorized admin

User is affected if WooCarousel Lite plugin is installed, has no nonce validation in its admin handlers, AND contains malicious stored scripts in plugin settings.

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

Implement nonces/tokens for all state-changing admin actions and apply proper input sanitization and output encoding to prevent XSS. Users should update to the latest patched version when available.

Recommended fix Moderate confidence

Latest available version of WIP WooCarousel Lite (newer than 1.1.7)

  1. Check if a newer version of the WIP WooCarousel Lite plugin is available in the WordPress plugin repository
  2. If a newer version exists, update the plugin to the latest version which should contain CSRF protection fixes
  3. If no update is available, consider temporarily disabling the plugin until a patched version is released
  4. Verify that all admin actions involving the plugin require proper authentication and authorization
Caveat Review plugin settings after upgrade as minor configuration changes may occur

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

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-30769 — 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-30769 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