CVE-2026-121519 · Package
NO FIX YET
The Social Slider Feed WordPress plugin up to and including 2.3.8 does not sanitize the slidespeed setting, and a missing capability check lets a Subscriber-level user overwrite it. The injected script then runs in the browser of every visitor who loads a page embedding the feed shortcode.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Social Slider Feed plugin at version 2.3.8 or earlier that allow subscriber accounts to exist. Exposure depends on the plugin being active and feed shortcodes being embedded on public pages. Sites without the plugin, or with it updated past the affected range, are not affected.
Not affected if no-subscriber-accounts, plugin-not-installed
Who cares self-hosted, social-slider-feed, wordpress
No fix yet, per the sources.
The Social Slider Feed – Social Media Feed & Gallery Widgets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'slidespeed' parameter in all versions up to, and including, 2.3.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The missing current_user_can() check in the Factory framework's connect() dispatcher allows Subscriber-level users to bypass the manage_options capability gate and both harvest a valid wis_edit_feed nonce and overwrite any feed's slidespeed setting, after which the stored payload fires on every public pageview embedding the feed shortcode.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.