PatchSiren cyber security CVE debrief
CVE-2026-84909 smub CVE debrief
The Custom Twitter Feeds – A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'buttoncolor' Shortcode Attribute in all versions up to, and including, 2.8.0. This is due to insufficient input sanitization and output escaping. Authenticated attackers with contributor-level access and above can inject arbitrary web scripts into pages, which will execute when 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, causing the ctf_statuses support_legacy_shortcode option to be set to boolean true by default and activating the unfiltered legacy shortcode attribute code path.
- Vendor
- smub
- Product
- Custom Twitter Feeds – A Tweets Widget or X Feed Widget
- CVSS
- MEDIUM 6.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-18
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-18
- Advisory updated
- 2026-09-18
Who should care
WordPress administrators and users with contributor-level access and above should assess their exposure to this vulnerability, especially if they have configured access tokens with zero or multiple legacy feeds.
Why it matters
CVE-2026-84909 is a Stored Cross-Site Scripting vulnerability in the Custom Twitter Feeds WordPress plugin. Authenticated attackers with contributor-level access can inject web scripts into pages, which execute when users access those pages. Defenders should verify exposure, restrict access, and prioritize remediation for installations using legacy feeds.
- Defenders must verify the presence of this vulnerability in their WordPress installations.
- Exploitation allows authenticated attackers to inject arbitrary web scripts into pages.
- Successful exploitation can lead to Cross-Site Scripting attacks on users accessing injected pages.
- Remediation priority is high for WordPress installations using the Custom Twitter Feeds plugin with legacy feeds configured.
Technical summary
The Custom Twitter Feeds plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'buttoncolor' Shortcode Attribute. This is due to insufficient input sanitization and output escaping. Authenticated attackers with contributor-level access and above can inject arbitrary web scripts into pages, which will execute when 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, causing the ctf_statuses support_legacy_shortcode option to be set to boolean true by default and activating the unfiltered legacy shortcode attribute code path. The vulnerability has a CVSS score of 6.4 and a MEDIUM
Defensive priority
Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations, especially if the Custom Twitter Feeds plugin is used with legacy feeds configured.
Recommended defensive actions
- Verify the presence of the Custom Twitter Feeds plugin in your WordPress installation.
- Check if the plugin version is 2.8.0 or earlier.
- Update the plugin to a version that fixes the vulnerability, if available.
- Review and restrict access to the WordPress admin interface to prevent exploitation.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and NVD entry provide details about the vulnerability, including its description, CVSS score, and references to source code. The Custom Twitter Feeds plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'buttoncolor' Shortcode Attribute. 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 The
Sources and references
Verified primary and authoritative sources
-
CVE-2026-84909 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-84909
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-84909 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-84909
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/custom-twitter-feed.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CTF_Parse.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CTF_Settings.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.8.0/inc/CtfFeed.php
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.