CVE-2026-116536: Custom Twitter Feeds (WordPress plugin) · Cross-site Scripting
Affects Custom Twitter Feeds (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 18 Nov 2026, 11:50 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 7.2 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| smubCustom Twitter Feeds – A Tweets Widget or X Feed Widget | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory for updates. Until a fix is available, restricting access to the Support page and limiting the execution of the ctf_feed_update cron job may reduce exposure. Applying input validation and output escaping at the application level could mitigate risk. Because this is a stored XSS vulnerability affecting administrator interfaces, caution is advised when granting access to the affected plugin's pages.
Description
The Custom Twitter Feeds – A Tweets Widget or X Feed Widget WordPress plugin is affected by a stored Cross-Site Scripting (XSS) vulnerability in all versions up to 2.11.1. This vulnerability arises from insufficient sanitization and escaping of the 'atts' JSON object, specifically the 'feed' key, allowing unauthenticated attackers to inject malicious scripts. The injected payload is stored in the database and executed later when an administrator accesses the Support page after a scheduled cron job runs.
References
- wordfence.com/threat-intel/vulnerabilities/id/03101d34-112b-4508-9aca-ade87c7a8853?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/Admin/CTF_Support.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/ctf-functions.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/CtfFeed.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/CtfCache.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/SB_Twitter_Cron_Updater.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/admin/views/support/content.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3799152%40custom-twitter-feeds&new=3799152%40custom-twitter-feeds (opens in a new tab)