Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12590: CWE-352 Cross-Site Request Forgery (CSRF) in andreaferracani YSlider

0
Medium
VulnerabilityCVE-2025-12590cvecve-2025-12590cwe-352
Published: Tue Nov 11 2025 (11/11/2025, 03:30:42 UTC)
Source: CVE Database V5
Vendor/Project: andreaferracani
Product: YSlider

Description

The YSlider plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting in all versions up to, and including, 1.1. This is due to missing nonce verification on the content configuration page and insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages via a forged request granted they can trick an administrator into performing an action such as clicking on a link. The injected scripts will execute whenever a user accesses an injected page.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 20:48:54 UTC

Technical Analysis

CVE-2025-12590 affects the YSlider plugin for WordPress, a popular content slider tool used to enhance website visuals. The vulnerability arises from a lack of nonce verification on the plugin's content configuration page, which is critical for preventing CSRF attacks. Without this protection, attackers can craft malicious requests that, when executed by an administrator (via clicking a link), inject arbitrary JavaScript into the site’s content. Additionally, the plugin fails to properly sanitize and escape input/output, enabling the stored XSS payload to persist in the site’s pages. This stored XSS can execute in the browsers of any visitors to the compromised pages, potentially stealing cookies, performing actions on behalf of users, or delivering malware. The CVSS 3.1 score of 6.1 reflects a medium severity, considering the attack vector is network-based, requires no privileges but does require user interaction, and impacts confidentiality and integrity but not availability. The vulnerability affects all versions up to and including 1.1 of YSlider. No patches or fixes are currently linked, and no known exploits have been observed in the wild, but the risk remains significant due to the widespread use of WordPress and the common administrative roles targeted in CSRF attacks.

Potential Impact

The primary impact of this vulnerability is the potential for attackers to inject persistent malicious scripts into WordPress sites using the YSlider plugin. This can lead to session hijacking, theft of sensitive user data, unauthorized actions performed on behalf of users, and defacement or reputational damage to affected websites. Since the attack requires an administrator to be tricked into clicking a malicious link, targeted attacks against site administrators are likely. The stored XSS payload can affect any visitor to the compromised pages, broadening the scope of impact. Organizations relying on YSlider for content display risk compromise of their web properties, loss of user trust, and potential regulatory consequences if user data is exposed. The vulnerability does not affect availability directly but undermines confidentiality and integrity, which can have cascading effects on business operations and security posture.

Mitigation Recommendations

Immediate mitigation steps include disabling or removing the YSlider plugin until a patched version is released. Administrators should be trained to avoid clicking suspicious links and use multi-factor authentication to reduce risk. Implementing Web Application Firewall (WAF) rules to detect and block CSRF and XSS attack patterns targeting the plugin’s endpoints can provide temporary protection. Site owners should audit their content for injected scripts and clean any malicious code found. Enforcing strict Content Security Policy (CSP) headers can help mitigate the impact of stored XSS by restricting script execution sources. Monitoring administrative actions and access logs for unusual activity can aid early detection. Once available, promptly applying official patches or updates from the plugin developer is critical. Additionally, plugin developers should implement nonce verification and robust input validation and output encoding to prevent similar issues in the future.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-31T22:37:48.878Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6912b13114bc3e00ba783d7b

Added to database: 11/11/2025, 3:44:49 AM

Last enriched: 2/27/2026, 8:48:54 PM

Last updated: 3/26/2026, 10:05:40 AM

Views: 48

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses