Cross-Site Request Forgery (CSRF) vulnerability in MetaSlider Responsive Slider by MetaSlider ml-slider allows Cross Site Request Forgery.This issue affects Responsive Slider by MetaSlider: from n/a through <= 3.92.0.
Security readout for executives and security teams
Plain-English summary
CVE-2025-24533 is a CSRF flaw in the WordPress MetaSlider Responsive Slider plugin, affecting versions through 3.92.0. A victim must be tricked into interacting with malicious content while authenticated. Reported impact is limited integrity and availability, not data disclosure. No active exploitation is indicated in the provided sources.
Executive priority
Treat as a moderate WordPress hygiene issue. It is not currently evidenced as actively exploited, but affected sites should be identified and updated once vendor guidance confirms the fix. Prioritize public-facing business sites with frequent administrator access.
Technical view
The issue is CWE-352 Cross-Site Request Forgery in package ml-slider. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity and availability impact. Sources identify affected versions as <= 3.92.0 but do not provide a confirmed fixed version in the bundle.
Likely exposure
Exposure is limited to WordPress sites running Responsive Slider by MetaSlider / ml-slider at version 3.92.0 or earlier. Risk is higher where administrators or privileged users remain logged in and can be lured to attacker-controlled pages.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. CSRF typically depends on social engineering an authenticated user’s browser into sending an unwanted request. The exact vulnerable action is not described in the supplied data.
Researcher notes
Evidence is sparse. The bundle confirms CSRF, affected plugin, affected version range, CVSS, and Patchstack reference, but not the vulnerable endpoint, nonce failure details, proof of concept, or fixed version. Avoid assuming exploitability beyond authenticated-user CSRF conditions.
Mitigation direction
Inventory WordPress sites for the MetaSlider ml-slider plugin and record installed versions.
Prioritize sites running MetaSlider 3.92.0 or earlier for review.
Check MetaSlider and Patchstack guidance for a fixed version or vendor-recommended mitigation.
Update the plugin if a vendor-supported patched release is available.
Limit admin sessions and require users to log out when not actively managing WordPress.
Validation and detection
Confirm whether ml-slider is installed on each WordPress site.
Verify the installed MetaSlider version is greater than 3.92.0, if a patched release exists.
Review vendor release notes for CVE-2025-24533 remediation details.
Check security monitoring for suspicious administrative changes around sliders or plugin settings.
Do not rely on exploitation tests unless authorized and safely scoped.
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.
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.
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.
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.