{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12008 exists.","fix":"No fix has been published for CVE-2024-12008 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-12008 is a medium-severity vulnerability in boldgrid W3 Total Cache, published on 14 Jan 2025. 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-12008 and fix it if it is affected.\n\nWhat it is: CVE-2024-12008 is a medium-severity vulnerability in boldgrid W3 Total Cache, published on 14 Jan 2025. 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-12008 exists.\n\nAffected product: boldgrid W3 Total Cache. 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-12008/ (Markdown: https://insights.sbomify.com/CVE-2024-12008/index.md)","id":"CVE-2024-12008","markdown":"https://insights.sbomify.com/CVE-2024-12008/index.md","name":"CVE-2024-12008","record":{"aliases":["GHSA-crhx-c2pr-jp56"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can view sensitive data in exposed debug logs if the feature is enabled, potentially aiding CSRF attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"w3_total_cache","vendor":"boldgrid"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.8.1 through the publicly exposed debug log file. This makes it possible for unauthenticated attackers to view potentially sensitive information in the exposed log file. For example, the log file may contain nonce values that can be used in further CSRF attacks.\r\nNote: the debug feature must be enabled for this to be a concern, and it is disabled by default.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-03-11","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2025-03-11T14:01:02Z","kind":"github_poc","ref":"https://github.com/spyata123/CVE-2024-12008-information-exposure-vulnerability-in-W3-Total-Cache","stars":0,"title":"CVE-2024-12008 information exposure vulnerability in W3 Total Cache"},{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-12008.yaml","stars":null,"title":"W3 Total Cache \u003c 2.8.2 - Log File Exposure"}],"tier":"weaponised"},"has_fix":null,"headline":"W3 Total Cache \u003c= 2.8.1 Information Exposure via Log Files","id":"CVE-2024-12008","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in EX5601-T1 firmware","id":"CVE-2024-12009"},"packages":[],"prev":{"headline":"code-projects Farmacia visualizar-produto.php sql injection","id":"CVE-2024-12007"},"products":["W3 Total Cache"],"published":"2025-01-14","related":[{"cvss_score":8.5,"headline":"W3 Total Cache \u003c= 2.8.1 - Authenticated (Subscriber+) Missing Authorization to Server-Side Request Forgery","id":"CVE-2024-12365","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":7.5,"headline":"Information disclosure in Total Cache","id":"CVE-2012-6077","kev_date_added":null,"published":"2019-11-22"},{"cvss_score":7.5,"headline":"Information disclosure in Total Cache","id":"CVE-2012-6078","kev_date_added":null,"published":"2019-11-22"},{"cvss_score":7.5,"headline":"Information disclosure in Total Cache","id":"CVE-2012-6079","kev_date_added":null,"published":"2019-11-22"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2019-6715","kev_date_added":null,"published":"2019-04-01"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2014-9414","kev_date_added":null,"published":"2014-12-24"},{"cvss_score":6.1,"headline":"W3 Total Cache \u003c 2.1.4 - Reflected XSS in Extensions Page (Attribute Context)","id":"CVE-2021-24436","kev_date_added":null,"published":"2021-07-19"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["boldgrid"]},"summary":"Unauthenticated attackers can view sensitive data in exposed debug logs if the feature is enabled, potentially aiding CSRF attacks.","url":"https://insights.sbomify.com/CVE-2024-12008/"}