CVE-2026-1885
Stored XSS in Slideshow WP Plugin via sswpid Shortcode Attribute
Publication date: 2026-02-11
Last updated on: 2026-02-11
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wp_slideshow | slideshow_wp | to 1.1 (inc) |
Helpful Resources
Exploitability
| 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?
The Slideshow Wp plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in the 'sswpid' attribute of the 'sswp-slide' shortcode in all versions up to and including 1.1.
This vulnerability arises because the plugin does not properly sanitize or escape user-supplied input for this attribute.
As a result, authenticated attackers with contributor-level access or higher can inject arbitrary web scripts into pages. These scripts execute whenever any user accesses the affected page.
How can this vulnerability impact me? :
This vulnerability allows attackers with contributor-level access or above to inject malicious scripts into pages via the slideshow shortcode.
When other users visit these pages, the injected scripts execute in their browsers, potentially leading to theft of sensitive information, session hijacking, or other malicious actions.
Because the attack is stored, the malicious script persists on the site until removed, affecting all visitors to the compromised pages.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability exists in the Slideshow WP plugin for WordPress, specifically in the 'sswpid' attribute of the 'sswp-slide' shortcode. Detection involves identifying if this plugin is installed and active on your WordPress site and if the version is up to and including 1.1.
To detect potential exploitation attempts or presence of malicious scripts injected via this vulnerability, you can search for suspicious or unexpected script tags or JavaScript code in pages or posts that use the shortcode [sswp-slide sswpid=ID].
Suggested commands to detect the plugin and potentially vulnerable shortcode usage include:
- On the server, search for the plugin directory: `ls wp-content/plugins/slideshow-wp`
- Check the plugin version by inspecting the plugin header in the main plugin file or via WordPress admin.
- Search the WordPress database for posts or pages containing the vulnerable shortcode: `wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[sswp-slide sswpid=%'"` (using WP-CLI or direct SQL)
- Scan the content of posts/pages for suspicious script injections: `wp db query "SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%<script>%' AND post_content LIKE '%[sswp-slide sswpid=%'"`
Network detection of exploitation attempts is difficult without specific signatures, but monitoring HTTP requests for unusual parameters or payloads targeting the 'sswpid' attribute in POST or GET requests to WordPress endpoints may help.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Update the Slideshow WP plugin to a version later than 1.1 where the vulnerability is fixed, if such an update is available.
- If an update is not available, temporarily deactivate or uninstall the Slideshow WP plugin to prevent exploitation.
- Restrict contributor-level and higher user permissions to trusted users only, as exploitation requires authenticated contributor-level access.
- Review and sanitize existing content using the [sswp-slide sswpid=ID] shortcode for injected scripts and remove any malicious code.
- Implement Web Application Firewall (WAF) rules to block suspicious input targeting the 'sswpid' attribute or attempts to inject scripts via shortcodes.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know