Skip to main content
VulnerabilityPublished

CVE-2026-4089: Twittee Text Tweet (WordPress plugin) · Cross-site Scripting

Affects Twittee Text Tweet (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 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
johnnie2uTwittee Text TweetAffected
  • <=1.0.8
Fixed in–

AI-suggested

Users should monitor the vendor's advisory channels for updates. Until a fix is released, restrict Contributor-level access to trusted users only and consider disabling or removing the Twittee Text Tweet plugin to prevent exploitation. Avoid using the vulnerable shortcode attributes in content.

Description

The Twittee Text Tweet WordPress plugin up to version 1.0.8 contains a stored cross-site scripting (XSS) vulnerability due to improper sanitization and escaping of user-supplied shortcode attributes. Authenticated users with Contributor-level access or higher can inject malicious scripts via the 'id' shortcode attribute and other attributes like 'tweet', 'content', 'balloon', and 'theme'. These scripts execute in the context of any user viewing the affected page. The vulnerability arises because the plugin uses extract() on shortcode attributes and directly inserts them into HTML and inline JavaScript without proper escaping. This can lead to arbitrary script execution and potential compromise of user sessions or site integrity.

References

Community reviews

Loading reviews…