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

AILast updated: 11/18/2025, 04:22:19 UTC

Technical Analysis

CVE-2025-12590 is a vulnerability in the YSlider WordPress plugin developed by andreaferracani, affecting all versions up to and including 1.1. The flaw arises from missing nonce verification on the plugin's content configuration page combined with inadequate input sanitization and output escaping. This creates a Cross-Site Request Forgery (CSRF) vector that enables unauthenticated attackers to craft malicious requests that, when executed by an administrator (via clicking a link or visiting a malicious page), inject stored Cross-Site Scripting (XSS) payloads into the website content. These injected scripts persist and execute in the context of any user visiting the infected page, potentially allowing attackers to steal session cookies, perform actions on behalf of users, or deliver further malware. The vulnerability does not require prior authentication but does require user interaction from an administrator, making social engineering a likely exploitation method. The CVSS 3.1 score of 6.1 reflects a medium severity with network attack vector, low attack complexity, no privileges required, user interaction required, and a scope change indicating the vulnerability affects components beyond the initially vulnerable plugin. No patches or known exploits are currently reported, but the risk remains significant due to the widespread use of WordPress and the plugin. The vulnerability is classified under CWE-352 (CSRF).

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to websites using the YSlider plugin on WordPress. Successful exploitation can lead to persistent XSS attacks, enabling attackers to hijack user sessions, deface websites, or conduct phishing campaigns leveraging the trusted domain. This can damage brand reputation, lead to data leakage, and potentially facilitate further network intrusion if administrative credentials or session tokens are compromised. Since the attack requires tricking an administrator, organizations with less stringent administrative security awareness or lacking multi-factor authentication are more vulnerable. The impact on availability is minimal, but confidentiality and integrity of web content and user data are at risk. Given the popularity of WordPress in Europe, especially among SMEs and public sector websites, the threat could affect a broad range of sectors including government, education, and commerce. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as exploit code may emerge.

Mitigation Recommendations

1. Immediately audit all WordPress sites for the presence of the YSlider plugin and identify versions in use. 2. Disable or remove the YSlider plugin until a security patch is released. 3. Implement strict input validation and output escaping on all plugin-managed content fields to prevent script injection. 4. Add nonce verification to all state-changing requests in the plugin to prevent CSRF attacks. 5. Educate administrators on phishing and social engineering risks to reduce the likelihood of clicking malicious links. 6. Enforce multi-factor authentication (MFA) for WordPress admin accounts to limit the impact of compromised credentials. 7. Monitor web server logs and admin activity for suspicious requests or unusual behavior. 8. Use web application firewalls (WAFs) with rules to detect and block CSRF and XSS attack patterns targeting the plugin. 9. Keep WordPress core and all plugins updated regularly to reduce exposure to known vulnerabilities. 10. Consider restricting administrative access by IP or VPN to reduce attack surface.

Need more detailed analysis?Get 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: 11/18/2025, 4:22:19 AM

Last updated: 11/20/2025, 9:38:56 AM

Views: 13

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats