CVE-2026-6177: Custom Twitter Feeds <= 2.5.4 - Unauthenticated Stored Cross-Site Scripting via Cached Tweet Text
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 CTFDisplayElements::getposttext() function when rendering cached tweet text. The plugin's ctfgetmoreposts 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-6177?
CVE-2026-6177 has a medium severity level due to its potential for stored Cross-Site Scripting attacks.
How do I fix CVE-2026-6177?
To fix CVE-2026-6177, upgrade the Custom Twitter Feeds plugin to version 2.5.5 or later.
What type of vulnerability is CVE-2026-6177?
CVE-2026-6177 is classified as an unauthenticated stored Cross-Site Scripting (XSS) vulnerability.
Who is affected by CVE-2026-6177?
Users of the Custom Twitter Feeds plugin for WordPress versions up to and including 2.5.4 are affected by CVE-2026-6177.
Can CVE-2026-6177 be exploited remotely?
Yes, CVE-2026-6177 can be exploited remotely by attackers without authentication.