{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49216 exists.","fix":"No fix has been published for CVE-2024-49216 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-49216 is a critical vulnerability in jclay06 Feed Comments Number, published on 16 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-49216 and fix it if it is affected.\n\nWhat it is: CVE-2024-49216 is a critical vulnerability in jclay06 Feed Comments Number, published on 16 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49216 exists.\n\nAffected product: jclay06 Feed Comments Number. 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-49216/ (Markdown: https://insights.sbomify.com/CVE-2024-49216/index.md)","id":"CVE-2024-49216","markdown":"https://insights.sbomify.com/CVE-2024-49216/index.md","name":"CVE-2024-49216","record":{"aliases":["GHSA-3wm3-96hr-g3vq"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can upload malicious web shells via the Feed Comments Number plugin, leading to remote code execution on the WordPress server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Unrestricted Upload of File with Dangerous Type vulnerability in jclay06 Feed Comments Number feed-comments-number allows Upload a Web Shell to a Web Server.This issue affects Feed Comments Number: from n/a through \u003c= 0.2.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WordPress Feed Comments Number plugin \u003c= 0.2.1 - Arbitrary File Upload vulnerability","id":"CVE-2024-49216","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Adding drop down roles in registration plugin \u003c= 1.1 - Privilege Escalation vulnerability","id":"CVE-2024-49217"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2024-49214"},"products":["Feed Comments Number"],"published":"2024-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-12","vendors":["jclay06"]},"summary":"Attackers can upload malicious web shells via the Feed Comments Number plugin, leading to remote code execution on the WordPress server.","url":"https://insights.sbomify.com/CVE-2024-49216/"}