HomeWordPress vulnerabilitiesCustom Twitter Feeds
Custom Twitter Feeds vulnerabilities
Custom Twitter Feeds has 5 known vulnerabilities in this database. The most recent published record is dated 18 Sep 2026.
- Known vulnerabilities
- 5
- Active installs
- 100,000+
- Latest version
- 2.10.0
- Last updated
- 30 Sep 2026
- Most recent
- 18 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-84909 | Medium 6.4 | Up to 2.8.0 | Fixed in a later version (latest 2.10.0) | 18 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-6177 | High 7.2 | Up to 2.5.4 | Fixed in a later version (latest 2.10.0) | 13 May 2026 |
| Cross-site request forgery (CSRF) CVE-2025-1314 | Medium 4.3 | Up to 2.2.5 | Fixed in a later version (latest 2.10.0) | 20 Mar 2025 |
| Cross-site scripting (XSS) CVE-2024-8983 | Medium 4.8 | Before 2.2.3 | Fixed in 2.2.3 | 8 Oct 2024 |
| Cross-site request forgery (CSRF) CVE-2024-0379 | Medium 4.3 | Before 2.2.2 | Fixed in 2.2.2 | 29 Feb 2024 |
Read the published descriptions
- CVE-2026-84909, 18 Sep 2026
- The Custom Twitter Feeds - A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'buttoncolor' Shortcode Attribute in all versions up to, and including, 2.8.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. This vulnerability is exploitable on common installs where the admin has configured access tokens with zero or multiple legacy feeds, as this causes the ctf_statuses support_legacy_shortcode option to be set to boolean true by default, activating the unfiltered legacy shortcode attribute code path. CVE record
- CVE-2026-6177, 13 May 2026
- 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 record
- CVE-2025-1314, 20 Mar 2025
- The Custom Twitter Feeds - A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.5. This is due to missing or incorrect nonce validation on the ctf_clear_cache_admin() function. This makes it possible for unauthenticated attackers to reset the plugin's cache via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2024-8983, 8 Oct 2024
- Custom Twitter Feeds WordPress plugin before 2.2.3 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2024-0379, 29 Feb 2024
- The Custom Twitter Feeds - A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.1. This is due to missing or incorrect nonce validation on the ctf_auto_save_tokens function. This makes it possible for unauthenticated attackers to update the site's twitter API token and secret via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
What to do if you run Custom Twitter Feeds
If you run Custom Twitter Feeds, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Custom Twitter Feeds vulnerabilities
Free. We email you when a new vulnerability is published for Custom Twitter Feeds, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.