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

CVE-2026-1911

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
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 Twitter Feeds plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tweet_title' parameter in the 'TwitterFeeds' shortcode in all versions up to, and including, 1.0.0 due to insufficient input sanitization and output escaping. 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 Twitter Feeds WordPress plugin up to version 1.0.0 has a stored XSS vulnerability in the 'tweet_title' parameter of the TwitterFeeds shortcode. Authenticated attackers with Contributor-level access can inject malicious JavaScript due to insufficient input sanitization and lack of output escaping, causing scripts to execute when users access affected pages.

MitigationUpdate to a patched version of the Twitter Feeds plugin that properly sanitizes the 'tweet_title' parameter and escapes output, or remove/deactivate the plugin if no patch is available.

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 Twitter Feeds plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Twitter Feeds' in the list. Note the installed version displayed.
    Affected if The Twitter Feeds plugin is present and active on the site
  2. Confirm plugin version is affected
    Compare the installed version shown in the plugins list to the affected range. The plugin versions up to and including 1.0.0 are vulnerable.
    Affected if Installed version is 1.0.0 or lower
  3. Identify use of vulnerable shortcode
    Search WordPress content (posts, pages, widgets) for the '[twitterfeeds]' or '[TwitterFeeds]' shortcode, particularly any instances containing the 'tweet_title' attribute.
    Affected if The TwitterFeeds shortcode with tweet_title parameter is in use on the site
  4. Inspect shortcode content for malicious input
    Examine the tweet_title parameter value in any found shortcode instances. Look for unsanitized HTML or JavaScript payloads (script tags, event handlers like onload, onerror, or javascript: URIs).
    Affected if The tweet_title parameter contains unsanitized script tags, event handlers, or suspicious JavaScript code
  5. Check for contributor-level user accounts
    Review WordPress user roles under Users > All Users. Identify any accounts with Contributor-level access who could have injected the malicious shortcode.
    Affected if There are Contributor-level users who could have authored the malicious content

The site is affected if the Twitter Feeds plugin version is 1.0.0 or lower AND the TwitterFeeds shortcode with a tweet_title parameter is being used, particularly if that parameter contains unsanitized input.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the Twitter Feeds plugin that properly sanitizes the 'tweet_title' parameter and escapes output, or remove/deactivate the plugin if no patch is available.

Recommended fix Moderate confidence

Version 1.0.1 or later (the first version after 1.0.0 that includes the security fix)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Twitter Feeds' plugin
  4. 4. Check if an update is available and update to the latest version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1911 — 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-1911 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