Skip to main content
VulnerabilityPublished

CVE-2026-6177: 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 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 13 May 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
smubCustom Twitter Feeds – A Tweets Widget or X Feed WidgetAffected
  • <=2.5.4
Fixed in–

AI-suggested

Until a fix is available, consider disabling or restricting access to the vulnerable AJAX endpoint or implementing web application firewall rules to block malicious payloads targeting this endpoint. Monitor vendor channels for an official patch or update.

Description

The Custom Twitter Feeds WordPress plugin (up to version 2.5.4) contains a stored cross-site scripting (XSS) vulnerability due to insufficient output escaping when rendering cached tweet text. An unauthenticated AJAX endpoint outputs cached tweet data without proper HTML escaping, allowing attackers to inject malicious scripts via tweets that get cached. This vulnerability can lead to arbitrary script execution in users' browsers when accessing the affected endpoint.

References

Community reviews

Loading reviews…