dbcve.org
Custom Twitter FeedsWordPress extension · Smashballoon

CVE-2024-49685

HIGH · 8.8 CVSS v3.1 Published 2024-10-31
Fix available
A fix is available. Upgrade to 2.2.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Custom Twitter Feeds WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings) by crafting malicious requests that the victim's browser automatically submits.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing form submissions and AJAX requests within the plugin; verify the WordPress nonce validation on admin actions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Custom Twitter FeedsWordPress extension
Affected:< 2.2.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    Log in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Custom Twitter Feeds' by Smashballoon in the list
    Affected if The plugin named 'Custom Twitter Feeds' or 'Smashballoon Custom Twitter Feeds' appears in the installed plugins list
  2. Check the installed version number
    In the Plugins page, click 'View Details' on the Custom Twitter Feeds plugin, or open the main plugin file (custom-twitter-feeds.php) and look for the 'Version' field in the plugin header comment
    Affected if The version displayed is a number less than 2.2.4 (for example, 2.2.3, 2.2.0, 1.9, etc.)
  3. Inspect plugin files for nonce validation (optional verification)
    Using a file manager or FTP, navigate to wp-content/plugins/custom-twitter-feeds/ and search PHP files for 'wp_verify_nonce' or 'check_admin_referer' functions, particularly in files handling form submissions or AJAX requests (such as files in the admin/ or includes/ folders)
    Affected if No nonce verification calls are found in files that handle settings changes or state-modifying actions, indicating CSRF protection is missing

You are affected if the Smashballoon Custom Twitter Feeds plugin is installed with a version number lower than 2.2.4, as this version range lacks anti-CSRF nonce validation on admin actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.4 or later
Fixed in 2.2.4
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing form submissions and AJAX requests within the plugin; verify the WordPress nonce validation on admin actions.

Recommended fix Moderate confidence

Custom Twitter Feeds plugin version 2.2.4

  1. Back up your WordPress site database and files before updating
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find 'Custom Twitter Feeds' (also known as 'Tweets Widget')
  5. Click 'Update now' if an update is available, or manually upload version 2.2.4
  6. After updating, verify the plugin is running version 2.2.4 or later under Plugins > Installed Plugins
  7. Test that Twitter feeds are rendering correctly on the frontend

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Custom Twitter Feeds Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49685 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data