Plugins · custom-twitter-feeds · data as of 2026-11-04
Is Custom Twitter Feeds safe? Known vulnerabilities and latest version
- Latest version
- 2.11.1
- Last updated
- 2026-11-02
- Active installs
- 100,000+
- Known issues on record
- 8
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Display X posts (Twitter tweets) from any public user account in a clean, attractive looking feed that updates weekly. — by Syed Balkhi
What to do
- Update to the latest version (2.11.1). Anything older than 2.9.0 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get custom-twitter-feeds --field=version shows what you run; wp plugin update custom-twitter-feeds updates it.
Check your version
Known vulnerabilities
8 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.4 CVE-2026-84909 · published 2026-09-18
Stored cross-site scripting (XSS) in Custom Twitter Feeds (2.8.0 and older)
- Affected
- 2.8.0 and older
- Fixed in
- 2.9.0 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-84909Wordfence advisoryCode change (fix)Plugin source
high 7.2 CVE-2026-6177 · published 2026-05-13
Stored cross-site scripting (XSS) in Custom Twitter Feeds (2.5.4 and older)
- Affected
- 2.5.4 and older
- Fixed in
- 2.5.5 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-6177Wordfence advisoryCode change (fix)Plugin source
medium 4.3 CVE-2025-1314 · published 2025-03-20
Cross-site request forgery (CSRF) in Custom Twitter Feeds (2.2.5 and older)
- Affected
- 2.2.5 and older
- Fixed in
- 2.3.0 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2025-1314Wordfence advisoryCode change (fix)wordpress.orgPlugin source
high 8.8 CVE-2024-49685 · published 2024-10-31
Cross-site request forgery (CSRF) in Custom Twitter Feeds (2.2.3 and older)
- Affected
- 2.2.3 and older
- Fixed in
- 2.2.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Syed Balkhi Custom Twitter Feeds (Tweets Widget) custom-twitter-feeds allows Cross Site Request Forgery.This issue affects Custom Twitter Feeds (Tweets Widget): from n/a through <= 2.2.3.
medium 4.8 CVE-2024-8983 · published 2024-10-08
Stored cross-site scripting (XSS) in Custom Twitter Feeds (older than 2.2.3)
- Affected
- older than 2.2.3
- Fixed in
- 2.2.3
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
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).
medium 4.3 CVE-2024-0379 · published 2024-02-29
Cross-site request forgery (CSRF) in Custom Twitter Feeds (2.2.1 and older)
- Affected
- 2.2.1 and older
- Fixed in
- 2.2.2 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2024-0379Wordfence advisoryCode change (fix)Plugin source
high 8.8 CVE-2023-52136 · published 2024-01-05
Cross-site request forgery (CSRF) in Custom Twitter Feeds (2.1.2 and older)
- Affected
- 2.1.2 and older
- Fixed in
- 2.2
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Smash Balloon Custom Twitter Feeds – A Tweets Widget or X Feed Widget.This issue affects Custom Twitter Feeds – A Tweets Widget or X Feed Widget: from n/a through 2.1.2.
high 8.8 CVE-2022-33974 · published 2023-05-29
Cross-site request forgery (CSRF) in Custom Twitter Feeds (1.8.4 and older)
- Affected
- 1.8.4 and older
- Fixed in
- 2.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Smash Balloon Custom Twitter Feeds (Tweets Widget) plugin <= 1.8.4 versions.
Recent activity
- 2026-11-02 — latest release on wordpress.org (2.11.1).
- 2026-09-18 — Stored cross-site scripting (XSS) disclosed (CVE-2026-84909), fixed in 2.9.0.
- 2026-05-13 — Stored cross-site scripting (XSS) disclosed (CVE-2026-6177), fixed in 2.5.5.
- 2025-03-20 — Cross-site request forgery (CSRF) disclosed (CVE-2025-1314), fixed in 2.3.0.
Get an email when Custom Twitter Feeds has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Custom Twitter Feeds (custom-twitter-feeds) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by Syed Balkhi (28 tracked)
Types found in this plugin: Cross-site request forgery (CSRF) (5) · Cross-site scripting (XSS) (3)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/custom-twitter-feeds (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/custom-twitter-feeds"><img src="https://laskyr.com/plugins/custom-twitter-feeds/badge.svg" alt="Custom Twitter Feeds vulnerability status"></a>