CVE-2026-84909
Custom Twitter Feeds <= 2.8.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'buttoncolor' Shortcode Attribute
- Published
- Updated
- Reserved
- Assigned by
- Wordfence
Description
The Custom Twitter Feeds – A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'buttoncolor' Shortcode Attribute in all versions up to, and including, 2.8.0 due to insufficient input sanitization and output escaping. 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. This vulnerability is exploitable on common installs where the admin has configured access tokens with zero or multiple legacy feeds, as this causes the ctf_statuses support_legacy_shortcode option to be set to boolean true by default, activating the unfiltered legacy shortcode attribute code path.
Timeline
ID reserved
By Wordfence
- 16 days later
· 16 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| WordfenceCNA (assigner) | 3.1 | Medium6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
| NVDNVD · Deferred | 3.1 | Medium6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
- EPSS (exploitation in 30 days)
- 0.41% · top 65% of all CVEs (7 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.4.
Weakness
Affected products
smub · Custom Twitter Feeds – A Tweets Widget or X Feed Widget
- affected ≤ 2.8.0
References (9)
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b1a9d042-c0c0-477a-8cdf-9fb9d2239059?source=cve (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CtfFeed.php#L2338 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CTF_Parse.php#L551 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CtfFeed.php#L2001 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CTF_Settings.php#L293 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CTF_Settings.php#L234 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CtfFeed.php#L139 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/custom-twitter-feed.php#L432 (opens in a new tab)
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3695675%40custom-twitter-feeds&old=3665650%40custom-twitter-feeds (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2026-84909)Record last updated .