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

CVE-2025-23810

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
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 Igor Sazonov Len Slider len-slider allows Reflected XSS.This issue affects Len Slider: from n/a through <= 2.0.11.

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 Len Slider WordPress plugin allows attackers to trick authenticated users into executing unintended actions that result in reflected XSS attacks through the slider component.

MitigationAdd anti-CSRF tokens to all state-changing operations and implement proper input sanitization and output encoding to prevent reflected XSS.

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 Len Slider plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or run 'wp plugin list' via WP-CLI, and look for 'Len Slider' in the list. Also check if the plugin files exist in /wp-content/plugins/len-slider/
    Affected if Len Slider plugin is not installed or not present in the plugin directory
  2. Identify the installed version
    Open the main plugin file (usually len-slider.php) in /wp-content/plugins/len-slider/ and locate the 'Version' header in the plugin comment block, or run 'grep -i "Version" /wp-content/plugins/len-slider/len-slider.php'
    Affected if The installed version does not match or cannot be verified against known patched versions
  3. Verify slider component is enabled
    Check if any slider post type or shortcode is published and publicly accessible. Look for published 'lslider' post types in the WordPress admin or check for active shortcodes like [len_slider] on any published pages
    Affected if No sliders are published or the slider component is not accessible to unauthenticated users
  4. Check for CSRF token implementation
    Review the plugin source code for presence of nonces and CSRF tokens in state-changing functions (slider save, update, delete operations). Search for 'wp_nonce' or '_wpnonce' in the plugin's PHP files
    Affected if State-changing operations lack CSRF token validation and the plugin handles authenticated requests

The environment is affected if the Len Slider plugin is installed and active, lacks CSRF protections in its slider management functions, and has accessible slider components that could be leveraged for reflected XSS attacks.

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

Add anti-CSRF tokens to all state-changing operations and implement proper input sanitization and output encoding to prevent reflected XSS.

Recommended fix Moderate confidence

Latest version of Len Slider (version higher than 2.0.11)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Len Slider' in the plugin list
  4. Check if an update is available for the Len Slider plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. If no update is visible in WordPress, manually download the latest version from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin is functioning correctly on the frontend

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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