CVE-2025-12590 MEDIUM

CVE-2025-12590: YSlider <= 1.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting

Vendor Andreaferracani
Product YSlider
Weakness CWE-352 · CSRF
Published November 11, 2025
Last update April 8, 2026

CVSS base score

6.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

YSlider versions 1.1 and earlier are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the slider without their knowledge. The attack requires the victim to visit the attacker's page while authenticated to the site.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on YSlider (such as modifying or deleting sliders) by tricking an authenticated admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify or delete sliders without permission if an admin visits a malicious link while logged in.

Conditions required to exploit

05Prerequisites

The site admin must be logged in and visit a page controlled by the attacker (e.g., via a phishing link or malicious ad).

Key dates

06Disclosure timeline

November 11, 2025 CVE published
April 8, 2026 Record updated