WordPress plugin · Updated daily · Source: Wordfence Intelligence

Custom Twitter Feeds vulnerabilities: affected versions and fixes

Custom Twitter Feeds has 100,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Custom Twitter Feeds at a glance

  • 10 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Nov 17, 2026.
  • Ranked #319 by popularity on WordPress.org (100,000+ active installs).
  • The latest version is 2.12.0 (released Nov 12, 2026). The most recent security fix shipped in 2.12.0.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Custom Twitter Feeds version

Enter the Custom Twitter Feeds version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Custom Twitter Feeds”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Custom Twitter Feeds”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.12.0). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Custom Twitter Feeds vulnerabilities

  • Custom Twitter Feeds <= 2.11.1 - Unauthenticated Stored Cross-Site Scripting via 'atts[feed]' Parameter

    Cross-site scripting (XSS) · CVE-2026-116536

    Affected versions: ≤ 2.11.1

    Fixed in: 2.12.0

    Severity: High 7.2 · Disclosed Nov 17, 2026

  • Custom Twitter Feeds <= 2.8.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'buttoncolor' Shortcode Attribute

    Cross-site scripting (XSS) · CVE-2026-84909

    Affected versions: ≤ 2.8.0

    Fixed in: 2.9.0

    Severity: Medium 6.4 · Disclosed Sep 17, 2026

  • Custom Twitter Feeds <= 2.5.4 - Unauthenticated Stored Cross-Site Scripting via Cached Tweet Text

    Cross-site scripting (XSS) · CVE-2026-6177

    Affected versions: ≤ 2.5.4

    Fixed in: 2.5.5

    Severity: High 7.2 · Disclosed May 12, 2026

  • Custom Twitter Feeds <= 2.2.5 - Cross-Site Request Forgery to Cache Reset via ctf_clear_cache_admin Function

    Cross-site request forgery (CSRF) · CVE-2025-1314

    Affected versions: ≤ 2.2.5

    Fixed in: 2.3.0

    Severity: Medium 4.3 · Disclosed Mar 19, 2025

  • Custom Twitter Feeds (Tweets Widget) <= 2.2.3 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2024-49685

    Affected versions: ≤ 2.2.3

    Fixed in: 2.2.4

    Severity: Medium 4.3 · Disclosed Oct 21, 2024

  • Custom Twitter Feeds – A Tweets Widget or X Feed Widget <= 2.2.2 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-8983

    Affected versions: ≤ 2.2.2

    Fixed in: 2.2.3

    Severity: Medium 4.8 · Disclosed Sep 17, 2024

  • Custom Twitter Feeds – A Tweets Widget or X Feed Widget <= 2.2.1 - Cross-Site Request Forgery to Plugin Options Update

    Cross-site request forgery (CSRF) · CVE-2024-0379

    Affected versions: ≤ 2.2.1

    Fixed in: 2.2.2

    Severity: Medium 4.3 · Disclosed Feb 6, 2024

  • Custom Twitter Feeds (Tweets Widget) <= 2.1.2 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2023-52136

    Affected versions: ≤ 2.1.2

    Fixed in: 2.2

    Severity: Medium 4.3 · Disclosed Dec 28, 2023

  • Custom Twitter Feeds (Tweets Widget) <= 1.8.4 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2022-33974

    Affected versions: < 2.0

    Fixed in: 2.0

    Severity: Medium 4.3 · Disclosed May 25, 2023

  • Smash Balloon Plugins (Various Versions) - Reflected Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: ≤ 1.8.1

    Fixed in: 1.8.2

    Severity: Medium 6.1 · Disclosed Jul 20, 2021

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 17, 2026.

Most common weaknesses in Custom Twitter Feeds

Cross-site scripting (XSS)

5 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Cross-site request forgery (CSRF)

5 issues

If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.

Frequently asked questions

Is Custom Twitter Feeds safe to use?

Custom Twitter Feeds is a well-known plugin with 100,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.12.0) and turn on automatic updates.

How do I find which version of Custom Twitter Feeds my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesCustom Twitter Feeds on WordPress.org