{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-0830 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0830 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0830 is a medium-severity vulnerability in nmedia Comments Extra Fields For Post,Pages and CPT, published on 13 Mar 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-0830 and fix it if it is affected.\n\nWhat it is: CVE-2024-0830 is a medium-severity vulnerability in nmedia Comments Extra Fields For Post,Pages and CPT, published on 13 Mar 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-0830 in the wild and no public exploit code.\n\nAffected product: nmedia Comments Extra Fields For Post,Pages and CPT. 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-0830/ (Markdown: https://insights.sbomify.com/CVE-2024-0830/index.md)","id":"CVE-2024-0830","markdown":"https://insights.sbomify.com/CVE-2024-0830/index.md","name":"CVE-2024-0830","record":{"aliases":["GHSA-rcmg-f2pm-c8pr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can trick administrators into modifying comment form fields and plugin settings via forged requests.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"comments_extra_fields_for_post\\,_pages_and_cpt","vendor":"najeebmedia"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Comments Extra Fields For Post,Pages and CPT plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.0. This is due to missing or incorrect nonce validation on several ajax actions. This makes it possible for unauthenticated attackers to invoke those actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. As a result, they may modify comment form fields and update plugin settings.","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":"Comments Extra Fields For Post,Pages and CPT \u003c= 5.0 - Cross-Site Request Forgery","id":"CVE-2024-0830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Vault May Expose Sensitive Information When Configuring An Audit Log Device","id":"CVE-2024-0831"},"packages":[],"prev":{"headline":"Comments Extra Fields For Post,Pages and CPT \u003c= 5.0 - Missing Authorization","id":"CVE-2024-0829"},"products":["Comments Extra Fields For Post,Pages and CPT"],"published":"2024-03-13","related":[{"cvss_score":4.3,"headline":"Comments Extra Fields For Post,Pages and CPT \u003c= 5.0 - Missing Authorization","id":"CVE-2024-0829","kev_date_added":null,"published":"2024-03-13"}],"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-08","vendors":["nmedia"]},"summary":"Unauthenticated attackers can trick administrators into modifying comment form fields and plugin settings via forged requests.","url":"https://insights.sbomify.com/CVE-2024-0830/"}