ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-6177

The Custom Twitter Feeds plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.5.4.

Published May 13, 2026 · catalog updated Jun 17, 2026 · The Custom Twitter Feeds

Check if you run it

No confirmed exploitation is on record for CVE-2026-6177. EPSS is 0.51%. Act only if a listed version of The Custom Twitter Feeds is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The Custom Twitter Feeds).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.2
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.51%
Remediation
Version ranges on file
Affected products
stated named in the record

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • stated named in the record<= 2.5.4

How to fix CVE-2026-6177

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-6177. EPSS is 0.51%. Act only if a listed version of The Custom Twitter Feeds is installed.

Which versions are affected?

Compare what you have installed with named in the record <= 2.5.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-79: Cross-site Scripting (XSS). EPSS 0.51%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 13, 2026 · NIST NVD

    Detected

    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() w

  2. Jun 17, 2026 · NIST NVD

    Updated

    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() w

Sources

  • CVE.orgVulnerability recordCVE-2026-6177

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-6177

    30-day exploitation probability 0.5%

    first.org
  • NIST NVDVulnerability recordCVE-2026-6177

    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_g

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.