LiveActive security incident?Get immediate response
CVE Record

CVE-2025-23810: WordPress Len Slider Plugin <= 2.0.11 - CSRF to Reflected Cross Site Scripting (XSS) vulnerability

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-23810 affects the WordPress Len Slider plugin. A vulnerable site can be exposed to a CSRF-assisted reflected XSS condition if a user is tricked into interacting with attacker-controlled content. The impact is rated high, but the provided sources do not show active exploitation or a confirmed fixed version.

Executive priority

Prioritize this for any public WordPress property using Len Slider, especially sites with administrator activity. Treat it as a high-risk hygiene item: confirm exposure quickly, remove or update if guidance exists, and avoid assuming exploitation without evidence.

Technical view

The CVE records a CWE-352 CSRF issue in Igor Sazonov Len Slider, affecting versions through 2.0.11, that allows reflected XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges required, user interaction required, and changed scope.

Likely exposure

Exposure is likely limited to WordPress sites running the Len Slider plugin at version 2.0.11 or earlier. Internet-facing WordPress sites have the highest practical concern because administrators and users may browse authenticated sessions from normal workstations.

Exploitation context

The source bundle does not cite CISA KEV listing or active exploitation. The CVSS vector requires user interaction, so risk depends on whether attackers can induce a site user or administrator to visit crafted content while the plugin is present.

Researcher notes

Evidence is narrow but clear on class and affected range: CSRF leading to reflected XSS, CWE-352, CVSS 7.1. The bundle does not provide endpoint details, proof of exploitation, or a named fixed release, so validation should remain inventory-based and non-invasive.

Mitigation direction

  • Inventory WordPress sites for Len Slider and record installed plugin versions.
  • For versions 2.0.11 or earlier, consult vendor or Patchstack guidance for update or removal options.
  • Temporarily disable the plugin where exposure is confirmed and business impact allows.
  • Review WordPress administrative session hygiene and avoid browsing untrusted links while authenticated.

Validation and detection

  • Check WordPress plugin inventories for the len-slider package.
  • Confirm installed Len Slider versions against the affected range through 2.0.11.
  • Review web logs and security tooling for unusual reflected XSS or CSRF-related alerts.
  • Document whether the plugin is active, inactive, removed, or replaced on each site.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-23810 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-23810Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Igor SazonovLen Sliderlen-slider, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.