{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6455 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6455 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6455 is a high-severity vulnerability in yudiz WP Contact Form 7 DB Handler, published on 28 May 2026. 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-2026-6455 and fix it if it is affected.\n\nWhat it is: CVE-2026-6455 is a high-severity vulnerability in yudiz WP Contact Form 7 DB Handler, published on 28 May 2026. 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-2026-6455 in the wild and no public exploit code.\n\nAffected product: yudiz WP Contact Form 7 DB Handler. 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-2026-6455/ (Markdown: https://insights.sbomify.com/CVE-2026-6455/index.md)","id":"CVE-2026-6455","markdown":"https://insights.sbomify.com/CVE-2026-6455/index.md","name":"CVE-2026-6455","record":{"aliases":["GHSA-xf5m-7grh-3gvm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"A CSRF vulnerability in WP Contact Form 7 DB Handler allows attackers to delete arbitrary files via SQL injection and deserialization flaws.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Contact Form 7 DB Handler plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Arbitrary File Deletion via SQL Injection and PHP Object Injection in versions up to and including 3.0. This is due to a missing nonce verification in the process_bulk_action() function, the nonce check is only executed when _wpnonce is present in the POST body, allowing it to be trivially bypassed by omitting the field, combined with the use of an unsanitized, unparameterized user-supplied value in a numeric SQL context (WHERE ID = $ID) and the unsafe deserialization of the query result's post_content field. An attacker can craft a CSRF page that tricks a logged-in administrator into triggering a UNION-based SQL injection payload (using CHAR() to avoid esc_sql quote-escaping) that returns a malicious serialized PHP array as post_content; upon deserialization, array values associated with keys containing 'ys_cfdbh_file' are used as file paths appended to the uploads directory path without any path traversal validation, and then passed to wp_delete_file(), allowing the attacker to delete arbitrary files on the server (e.g., wp-config.php, system files).","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":"Cross-site request forgery in WP Contact Form 7 DB Handler","id":"CVE-2026-6455","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Account Switcher \u003c= 1.0.2 - Authenticated (Subscriber+) Authentication Bypass to Privilege Escalation","id":"CVE-2026-6456"},"packages":[],"prev":{"headline":"Cross-site scripting in Firelight Lightbox","id":"CVE-2026-6454"},"products":["WP Contact Form 7 DB Handler"],"published":"2026-05-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-05-28","vendors":["yudiz"]},"summary":"A CSRF vulnerability in WP Contact Form 7 DB Handler allows attackers to delete arbitrary files via SQL injection and deserialization flaws.","url":"https://insights.sbomify.com/CVE-2026-6455/"}