{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12685 exists.","fix":"No fix has been published for CVE-2025-12685 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12685 is a medium-severity vulnerability in Unknown WPBookit, published on 2 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12685 and fix it if it is affected.\n\nWhat it is: CVE-2025-12685 is a medium-severity vulnerability in Unknown WPBookit, published on 2 Jan 2026. 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-2025-12685 exists.\n\nAffected product: Unknown WPBookit. 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-2025-12685/ (Markdown: https://insights.sbomify.com/CVE-2025-12685/index.md)","id":"CVE-2025-12685","markdown":"https://insights.sbomify.com/CVE-2025-12685/index.md","name":"CVE-2025-12685","record":{"aliases":["GHSA-6w96-gvjq-xh8h"],"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":"An unauthenticated attacker can delete any customer in the WPBookit WordPress plugin via a CSRF attack due to missing checks.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"The WPBookit WordPress plugin through 1.0.7 lacks a CSRF check when deleting customers. This could allow an unauthenticated attacker to delete any customer through 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":"WPBookit \u003c= 1.0.7 - Customer Deletion via CSRF","id":"CVE-2025-12685","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in BeeStation OS","id":"CVE-2025-12686"},"packages":[],"prev":{"headline":"URL Shortify \u003c 1.11.3 - Reflected XSS","id":"CVE-2025-12684"},"products":["WPBookit"],"published":"2026-01-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["Unknown"]},"summary":"An unauthenticated attacker can delete any customer in the WPBookit WordPress plugin via a CSRF attack due to missing checks.","url":"https://insights.sbomify.com/CVE-2025-12685/"}