{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12280 exists.","fix":"No fix has been published for CVE-2024-12280 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-12280 is a medium-severity vulnerability in Unknown WP Customer Area, published on 27 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-12280 and fix it if it is affected.\n\nWhat it is: CVE-2024-12280 is a medium-severity vulnerability in Unknown WP Customer Area, published on 27 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-12280 exists.\n\nAffected product: Unknown WP Customer Area. 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-12280/ (Markdown: https://insights.sbomify.com/CVE-2024-12280/index.md)","id":"CVE-2024-12280","markdown":"https://insights.sbomify.com/CVE-2024-12280/index.md","name":"CVE-2024-12280","record":{"aliases":["GHSA-f39m-g6qq-h3xv"],"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 force logged-in users to delete WP Customer Area logs via CSRF, compromising audit trails.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_customer_area","vendor":"marvinlabs"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","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 WP Customer Area WordPress plugin through 8.2.4 does not have CSRF check in place when deleting its logs, which could allow attackers to make a logged in to delete them via a CSRF attack","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":"WP Customer Area \u003c= 8.2.4 - Event Log Deletion via CSRF","id":"CVE-2024-12280","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Homey \u003c= 2.4.2 - Unauthenticated Privilege Escalation in homey_save_profile","id":"CVE-2024-12281"},"packages":[],"prev":{"headline":"WP Social AutoConnect \u003c= 4.6.2 - Cross-Site Request Forgery to Reflected Cross-Site Scripting","id":"CVE-2024-12279"},"products":["WP Customer Area"],"published":"2025-01-27","related":[{"cvss_score":6.5,"headline":"WP Customer Area \u003c 8.2.1 - Subscriber+ Account Address Leak","id":"CVE-2023-6824","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":6.1,"headline":"WP Customer Area \u003c= 8.2.2 - Reflected Cross-Site Scripting","id":"CVE-2024-0665","kev_date_added":null,"published":"2024-01-24"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-18519","kev_date_added":null,"published":"2019-08-20"},{"cvss_score":4.3,"headline":"WP Customer Area \u003c= 8.2.4 - Bulk Delete via CSRF","id":"CVE-2024-12436","kev_date_added":null,"published":"2025-01-27"},{"cvss_score":4.3,"headline":"WP Customer Area \u003c 8.2.1 - Subscriber+ Account Address Update","id":"CVE-2023-6741","kev_date_added":null,"published":"2024-01-16"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-28","vendors":["Unknown"]},"summary":"Attackers can force logged-in users to delete WP Customer Area logs via CSRF, compromising audit trails.","url":"https://insights.sbomify.com/CVE-2024-12280/"}