{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-12005 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-12005 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-12005 is a medium-severity vulnerability in zjhzxhz WP-BibTeX, published on 21 Jan 2025. 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-12005 and fix it if it is affected.\n\nWhat it is: CVE-2024-12005 is a medium-severity vulnerability in zjhzxhz WP-BibTeX, published on 21 Jan 2025. 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-12005 in the wild and no public exploit code.\n\nAffected product: zjhzxhz WP-BibTeX. 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-12005/ (Markdown: https://insights.sbomify.com/CVE-2024-12005/index.md)","id":"CVE-2024-12005","markdown":"https://insights.sbomify.com/CVE-2024-12005/index.md","name":"CVE-2024-12005","record":{"aliases":["GHSA-6mfr-g9g7-ccpv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick admins into executing malicious scripts via CSRF, leading to code execution or account takeover in WP-BibTeX.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp-bibtex","vendor":"infinitescript"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP-BibTeX plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0.1. This is due to missing or incorrect nonce validation on the wp_bibtex_option_page() function. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request 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":"WP-BibTeX \u003c= 3.0.1 - Cross-Site Request Forgery to Stored and Reflected Cross-Site Scripting","id":"CVE-2024-12005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in W3 Total Cache","id":"CVE-2024-12006"},"packages":[],"prev":{"headline":"WPC Order Notes for WooCommerce \u003c= 1.5.2 - Cross-Site Request Forgery to Reflected Cross-Site Scripting","id":"CVE-2024-12004"},"products":["WP-BibTeX"],"published":"2025-01-21","related":[{"cvss_score":6.4,"headline":"WP-BibTeX \u003c= 3.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-13578","kev_date_added":null,"published":"2025-02-18"}],"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":["zjhzxhz"]},"summary":"Attackers can trick admins into executing malicious scripts via CSRF, leading to code execution or account takeover in WP-BibTeX.","url":"https://insights.sbomify.com/CVE-2024-12005/"}