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

CVE-2026-6177

HIGH · 7.2 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 Custom Twitter Feeds plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.5.4. This is due to insufficient output escaping in the CTF_Display_Elements::get_post_text() function when rendering cached tweet text. The plugin's ctf_get_more_posts AJAX action is available to unauthenticated users and directly outputs cached tweet data through nl2br() without HTML escaping. When an attacker can get malicious content into cached tweet data (either by tweeting content that gets cached by the site's feed configuration, or through other vulnerabilities), the malicious HTML/JavaScript is executed when the unauthenticated endpoint is accessed. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses the affected endpoint.

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

Stored XSS vulnerability in Custom Twitter Feeds WordPress plugin where CTF_Display_Elements::get_post_text() fails to escape HTML when rendering cached tweet text. The unauthenticated ctf_get_more_posts AJAX endpoint outputs cached data via nl2br() without sanitization, allowing injection of malicious scripts that execute when users access the endpoint.

MitigationUpdate Custom Twitter Feeds plugin to version 2.5.5 or later which includes proper HTML escaping in the get_post_text() function. If immediate update is not possible, consider disabling the ctf_get_more_posts AJAX endpoint or implementing output sanitization at the web server level.

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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Custom Twitter Feeds plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Custom Twitter Feeds' or check the plugin files in /wp-content/plugins/custom-twitter-feeds/ for a version file
    Affected if The plugin is installed and active
  2. Determine installed plugin version
    Check the plugin header in custom-twitter-feeds.php or the WordPress plugin admin page for the version number
    Affected if Version is earlier than 2.5.5 (the fixed version)
  3. Confirm ctf_get_more_posts AJAX endpoint is exposed
    Access the URL /wp-admin/admin-ajax.php?action=ctf_get_more_posts or /wp-admin/admin-ajax.php?action=ctf_get_more_posts&ctf_get_most_recent=1 in a browser or via curl to see if it returns cached tweet data
    Affected if The endpoint returns data without requiring authentication or sanitization
  4. Inspect get_post_text function for missing escaping
    Examine the CTF_Display_Elements::get_post_text() method in the plugin source code - look for nl2br() calls without corresponding htmlspecialchars() or esc_html() sanitization
    Affected if The function uses nl2br() on user-supplied cached tweet text without HTML escaping

A user is affected if the Custom Twitter Feeds plugin versions before 2.5.5 are installed with the ctf_get_more_posts AJAX endpoint accessible and the get_post_text() function lacks HTML sanitization before nl2br() output.

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 Custom Twitter Feeds plugin to version 2.5.5 or later which includes proper HTML escaping in the get_post_text() function. If immediate update is not possible, consider disabling the ctf_get_more_posts AJAX endpoint or implementing output sanitization at the web server level.

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-6177 — 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-6177 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