Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-6177

CVE-2026-6177 - Custom Twitter Feeds Plugin

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. 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.

CVE-2026-6177

HIGH CVSS 7.2 Published 2026-05-13 Updated 2026-05-13
AI Risk High (80/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P2 Urgent
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Affected Components 1
Reference Links 10
AI Risk Engine High (80/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-05-13 CVE published and first recorded in the threat feed.
  2. 2026-05-13 Record updated with latest vulnerability metadata.
  3. 2026-05-23 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 8 days ago

AI enriched 8 days ago (2026-05-23 21:43 UTC)

Technical Summary

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,…

Potential Impact

Severity is HIGH (CVSS 7.2). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 80/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Custom Twitter Feeds PLUGIN · custom-twitter-feeds Affected: <= 2.5.4 Fixed version not specified

References

Scroll to top