dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4089

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Twittee Text Tweet plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' shortcode attribute in all versions up to and including 1.0.8. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. The ttt_twittee_tweeter() function uses extract() to pull shortcode attributes into local variables and then directly concatenates them into HTML output without any escaping. Specifically, the $id parameter is inserted into an HTML id attribute context without esc_attr(), allowing an attacker to break out of the attribute and inject arbitrary HTML event handlers. Additionally, the $tweet, $content, $balloon, and $theme attributes are similarly injected into inline JavaScript without escaping (lines 87, 93, 101, 117). This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Twittee Text Tweet WordPress plugin fails to sanitize shortcode attributes before outputting them in HTML and JavaScript contexts. The ttt_twittee_tweeter() function uses extract() to import shortcode parameters directly into local variables, then concatenates the $id parameter into an HTML id attribute without esc_attr(), and similarly injects $tweet, $content, $balloon, and $theme into inline JavaScript without escaping. This allows authenticated users with Contributor-level access to inject arbitrary scripts that execute on page view.

MitigationUpdate to the latest version of the plugin when available. Until then, remove any existing malicious shortcode instances from pages and posts, and restrict shortcode usage to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Twittee Text Tweet' or 'Twittee'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'twittee' in the name.
    Affected if The plugin is installed and active
  2. Check the installed version
    In Plugins list, find Twittee Text Tweet and note the version number displayed. Compare this to the latest version available at wordpress.org/plugins/twittee-text-tweet or the version noted in any security advisory.
    Affected if The installed version lacks the security fix for attribute escaping (pre-1.0.5 or unpatched version)
  3. Identify shortcode usage
    Search the wp_posts database table or use a plugin like Search Regex to find instances of the [twittee] shortcode in post_content. Also check wp_postmeta for custom field usage.
    Affected if The shortcode [twittee] or [twittee_tweet] is present in any published content
  4. Review contributor-level user accounts
    In WordPress admin, go to Users and review any accounts with the 'Contributor' role. Check if they have authored posts containing the twittee shortcode.
    Affected if Untrusted Contributor-level users exist and have created content with the shortcode

You are affected if the Twittee Text Tweet plugin is installed, contains the vulnerable shortcode in any content, and untrusted users have Contributor-level access to create or edit that content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin when available. Until then, remove any existing malicious shortcode instances from pages and posts, and restrict shortcode usage to trusted users only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4089 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data