Custom Twitter Feeds (Tweets Widget) <= 2.2.3 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.2.4
- Affected Plugin
- Custom Twitter Feeds – A Tweets Widget or X Feed Widget
- Affected Version
<= 2.2.3- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-49685
At a glance
CVE-2024-49685 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Custom Twitter Feeds WordPress plugin, affecting versions <= 2.2.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2.4; sites on affected versions should update now. Disclosed October 2024, reported by Rafie Muhammad.
Vulnerability Overview
The Custom Twitter Feeds (Tweets Widget) plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.2.3. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Custom Twitter Feeds <= 2.2.3 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Custom Twitter Feeds the fix is 2.2.4: builds <= 2.2.3 are affected, anything from 2.2.4 onward is not.
Remediation
Update to version 2.2.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Custom Twitter Feeds: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Custom Twitter Feeds 2.2.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 4.3CVE-2025-1314: Custom Twitter Feeds <= 2.2.5 CSRF to Cache Reset
CVE-2025-1314 - 4.3CVE-2024-0379: Custom Twitter Feeds CSRF to Plugin Options Update
CVE-2024-0379 - 4.3CVE-2023-52136: Custom Twitter Feeds (Tweets Widget) <= 2.1.2 CSRF
CVE-2023-52136 - 4.3CVE-2022-33974: Custom Twitter Feeds (Tweets Widget) <= 1.8.4 CSRF
CVE-2022-33974
Other vulnerabilities in Custom Twitter Feeds – A Tweets Widget or X Feed Widget
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C