CVE-2026-6177 Custom Twitter Feeds <= 2.5.4 - Unauthenticated Stored Cross-Site Scripting via Cached Tweet Text
Unauthenticated attackers can inject arbitrary web scripts via cached tweet text in the Custom Twitter Feeds WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-6177?
CVE-2026-6177 is a high-severity cross-site scripting vulnerability in smub Custom Twitter Feeds – A Tweets Widget or X Feed Widget, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Custom Twitter Feeds plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.5.4. This is due to insufficient output escaping in the CTF_Display_Elements::get_post_text() function when rendering cached tweet text. The plugin's ctf_get_more_posts AJAX action is available to unauthenticated users and directly outputs cached tweet data through nl2br() without HTML escaping. When an attacker can get malicious content into cached tweet data (either by tweeting content that gets cached by the site's feed configuration, or through other vulnerabilities), the malicious HTML/JavaScript is executed when the unauthenticated endpoint is accessed. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses the affected endpoint.
Weakness: CWE-79
Which versions are affected by CVE-2026-6177?
How do I fix CVE-2026-6177?
No fix has been published for CVE-2026-6177 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-6177 being exploited?
There is no known exploitation of CVE-2026-6177 in the wild and no public exploit code.