{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-9588 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-9588 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9588 is a medium-severity vulnerability in amu02aftab Category and Taxonomy Meta Fields, published on 22 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-9588 and fix it if it is affected.\n\nWhat it is: CVE-2024-9588 is a medium-severity vulnerability in amu02aftab Category and Taxonomy Meta Fields, published on 22 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-9588 in the wild and no public exploit code.\n\nAffected product: amu02aftab Category and Taxonomy Meta Fields. 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-9588/ (Markdown: https://insights.sbomify.com/CVE-2024-9588/index.md)","id":"CVE-2024-9588","markdown":"https://insights.sbomify.com/CVE-2024-9588/index.md","name":"CVE-2024-9588","record":{"aliases":["GHSA-gxw9-j8r3-33w6"],"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":"Attackers can trick administrators into adding or deleting taxonomy meta via CSRF, requiring user interaction to modify site data.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"category_and_taxonomy_meta_fields","vendor":"aftabhusain"}],"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":"The Category and Taxonomy Meta Fields plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.0. This is due to missing or incorrect nonce validation on the 'wpaft_option_page' function. This makes it possible for unauthenticated attackers to add and delete taxonomy meta, granted they can trick a site administrator into performing an action such as clicking on a link.","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":"Category and Taxonomy Meta Fields \u003c= 1.0.0 - Cross-Site Request Forgery to Taxonomy Meta Add/Delete","id":"CVE-2024-9588","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Category and Taxonomy Meta Fields \u003c= 1.0.0 - Authenticated (Administrator+) Stored Cross-Site Scripting","id":"CVE-2024-9589"},"packages":[],"prev":{"headline":"Linkz.ai \u003c= 1.1.8 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Update via AJAX","id":"CVE-2024-9587"},"products":["Category and Taxonomy Meta Fields"],"published":"2024-10-22","related":[{"cvss_score":5.5,"headline":"Category and Taxonomy Meta Fields \u003c= 1.0.0 - Authenticated (Administrator+) Stored Cross-Site Scripting","id":"CVE-2024-9589","kev_date_added":null,"published":"2024-10-22"},{"cvss_score":5.5,"headline":"Category and Taxonomy Meta Fields \u003c= 1.0.0 - Authenticated (Editor+) Stored Cross-Site Scripting","id":"CVE-2024-9590","kev_date_added":null,"published":"2024-10-22"}],"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":["amu02aftab"]},"summary":"Attackers can trick administrators into adding or deleting taxonomy meta via CSRF, requiring user interaction to modify site data.","url":"https://insights.sbomify.com/CVE-2024-9588/"}