{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-49685 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-49685 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-49685 is a medium-severity vulnerability in Syed Balkhi Custom Twitter Feeds (Tweets Widget), published on 31 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-49685 and fix it if it is affected.\n\nWhat it is: CVE-2024-49685 is a medium-severity vulnerability in Syed Balkhi Custom Twitter Feeds (Tweets Widget), published on 31 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-49685 in the wild and no public exploit code.\n\nAffected product: Syed Balkhi Custom Twitter Feeds (Tweets Widget). No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-49685/ (Markdown: https://insights.sbomify.com/CVE-2024-49685/index.md)","id":"CVE-2024-49685","markdown":"https://insights.sbomify.com/CVE-2024-49685/index.md","name":"CVE-2024-49685","record":{"aliases":["GHSA-jrrv-7qxg-9qwh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick authenticated users into performing unintended actions in the Custom Twitter Feeds WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"custom_twitter_feeds","vendor":"smashballoon"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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 \u003c= 2.2.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WordPress Custom Twitter Feeds plugin \u003c= 2.2.3 - Cross Site Request Forgery (CSRF) vulnerability","id":"CVE-2024-49685","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Landing Page Cat plugin \u003c= 1.7.4 - Broken Access Control vulnerability","id":"CVE-2024-49686"},"packages":[],"prev":{"headline":"WordPress Backup and Staging by WP Time Capsule plugin \u003c= 1.22.21 - PHP Object Injection vulnerability","id":"CVE-2024-49684"},"products":["Custom Twitter Feeds (Tweets Widget)"],"published":"2024-10-31","related":[{"cvss_score":5.4,"headline":"WordPress Custom Twitter Feeds (Tweets Widget) Plugin \u003c= 1.8.4 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2022-33974","kev_date_added":null,"published":"2023-05-29"},{"cvss_score":4.8,"headline":"Custom Twitter Feeds \u003c 2.2.3 - Admin+ Stored XSS","id":"CVE-2024-8983","kev_date_added":null,"published":"2024-10-08"},{"cvss_score":4.3,"headline":"Custom Twitter Feeds – A Tweets Widget or X Feed Widget \u003c= 2.2.1 - Cross-Site Request Forgery to Plugin Options Update","id":"CVE-2024-0379","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":4.3,"headline":"WordPress Custom Twitter Feeds (Tweets Widget) Plugin \u003c= 2.1.2 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-52136","kev_date_added":null,"published":"2024-01-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["Syed Balkhi"]},"summary":"Attackers can trick authenticated users into performing unintended actions in the Custom Twitter Feeds WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-49685/"}