Skip to main content
VulnerabilityPublished

CVE-2026-116536: Custom Twitter Feeds (WordPress plugin) · Cross-site Scripting

Affects Custom Twitter Feeds (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 18 Nov 2026, 11:50 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
smubCustom Twitter Feeds – A Tweets Widget or X Feed WidgetAffected
  • <=2.11.1
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

Community reviews

Loading reviews…