Skip to main content
CVE-2026-116536VulnerabilityPublished

The Custom Twitter Feeds – A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'atts (JSON object, specifically the inner `feed` key)' parameter in all versions up to, and including, 2.11.1 due to insufficient input sanitization and output escaping

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116536· High 7.2

Not known to be exploited · CVSS 7.2 High.

Data as of 18 Nov 2026, 13:49 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–

Description

The Custom Twitter Feeds – A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'atts (JSON object, specifically the inner `feed` key)' parameter in all versions up to, and including, 2.11.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is first stored in the wp_ctf_feed_caches database table and later written into the ctf_cron_report WordPress option by the scheduled ctf_feed_update cron job, meaning execution is deferred until the cron runs and an administrator subsequently loads the Support page.

References

Community reviews

Loading reviews…