CVE-2025-5291
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-06-17

Last updated on: 2025-07-02

Assigner: Wordfence

Description
The Master Slider – Responsive Touch Slider plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's masterslider_pb and ms_slide shortcodes in all versions up to, and including, 3.10.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-17
Last Modified
2025-07-02
Generated
2026-05-07
AI Q&A
2025-06-17
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
averta master_slider to 3.10.9 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-5291 is a Stored Cross-Site Scripting (XSS) vulnerability in the Master Slider – Responsive Touch Slider WordPress plugin, affecting all versions up to and including 3.10.8. The vulnerability arises because the plugin does not properly sanitize and escape user-supplied attributes in the masterslider_pb and ms_slide shortcodes. This allows authenticated users with contributor-level access or higher to inject arbitrary malicious scripts into pages. These scripts execute whenever any user accesses the infected page, potentially compromising site security. [3]


How can this vulnerability impact me? :

This vulnerability can allow an attacker with contributor-level access or higher to inject malicious scripts into WordPress pages via the vulnerable shortcodes. When other users visit these pages, the injected scripts execute in their browsers, potentially leading to session hijacking, defacement, data theft, or further compromise of the website. Since the attack requires authenticated access, it primarily impacts sites where contributors or similar roles are trusted but may be compromised or malicious. [3]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves Stored Cross-Site Scripting (XSS) via the 'masterslider_pb' and 'ms_slide' shortcodes in the Master Slider WordPress plugin versions up to 3.10.8. Detection can involve scanning WordPress content for usage of these shortcodes with suspicious or malicious script payloads in their attributes. You can search your WordPress database posts and pages for these shortcodes and check for suspicious script tags or encoded JavaScript. For example, using WP-CLI or direct database queries, you can run commands like: 1) wp search-replace --dry-run '<script' '' --path=/path/to/wordpress to find script tags, or 2) grep -r '\[masterslider_pb' /path/to/wordpress/wp-content/uploads or database exports. Additionally, monitoring HTTP requests for unusual payloads or unexpected script injections in pages using these shortcodes can help detect exploitation attempts. However, no specific detection commands are provided in the resources. [1, 3]


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to update the Master Slider plugin to version 3.10.9 or later, where the vulnerability has been fixed by improving output sanitization and escaping in shortcode handlers to prevent XSS attacks. If updating is not immediately possible, restrict contributor-level access and above to trusted users only, as the vulnerability requires authenticated contributor-level access. Additionally, consider applying Web Application Firewall (WAF) rules to block suspicious script injections and monitor for exploitation attempts. Ultimately, updating the plugin to the patched version is the recommended and most effective mitigation. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart