CVE-2026-6177 json
Custom Twitter Feeds <= 2.5.4 - Unauthenticated Stored Cross-Site Scripting via Cached Tweet Text
published 2026-05-13 5 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-29945
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- smub Custom Twitter Feeds – A Tweets Widget or X Feed Widget
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/e4b2178f-e4da-4bfb-9c27-8c1884499769?source=cve
- plugins.trac.wordpress.org /browser/custom-twitter-feeds/tags/2.5.4/custom-twitter-feed.php#L447
- plugins.trac.wordpress.org /browser/custom-twitter-feeds/trunk/inc/CTF_Display_Elements.php#L505
- plugins.trac.wordpress.org /browser/custom-twitter-feeds/tags/2.5.4/inc/CTF_Display_Elements.php#L505
- plugins.trac.wordpress.org /browser/custom-twitter-feeds/trunk/custom-twitter-feed.php#L447
- plugins.trac.wordpress.org /browser/custom-twitter-feeds/trunk/inc/CTF_Display_Elements.php#L521
- plugins.trac.wordpress.org /browser/custom-twitter-feeds/tags/2.5.4/inc/CTF_Display_Elements.php#L521
- plugins.trac.wordpress.org /browser/custom-twitter-feeds/trunk/templates/item.php#L36
- plugins.trac.wordpress.org /browser/custom-twitter-feeds/tags/2.5.4/templates/item.php#L36
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&new=3519584%40custom-twitter-feeds&old=3481416%40custom-twitter-fee
Sources
- CVE List CVE-2026-6177
- NVD CVE-2026-6177
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.