{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9618 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9618 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9618 is a medium-severity vulnerability in PeachPay — Payments \u0026 Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI), 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-9618 and fix it if it is affected.\n\nWhat it is: CVE-2026-9618 is a medium-severity vulnerability in PeachPay — Payments \u0026 Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI), 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-9618 in the wild and no public exploit code.\n\nAffected product: PeachPay — Payments \u0026 Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI). 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-9618/ (Markdown: https://insights.sbomify.com/CVE-2026-9618/index.md)","id":"CVE-2026-9618","markdown":"https://insights.sbomify.com/CVE-2026-9618/index.md","name":"CVE-2026-9618","record":{"aliases":["GHSA-2wqg-w33r-qx37"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress payment plugin","requires_auth":"none","summary":"Attackers can trick admins into deleting Stripe credentials, disabling payment processing for the store.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","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 PeachPay — Payments \u0026 Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.120.46. This is due to missing or incorrect nonce validation on the peachpay_stripe_handle_admin_actions function. This makes it possible for unauthenticated attackers to permanently delete all stored Stripe credentials — including publishable keys, secret keys, webhook secrets, and Apple Pay configuration — from the WordPress database, disabling Stripe payment processing for the store 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":"2026-10-21","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-21T02:02:58Z","kind":"github_poc","ref":"https://github.com/SleepTheGod/cve-2026-9618-Patch","stars":0,"title":"cve-2026-9618 Poc Patch"}],"tier":"poc_unverified"},"has_fix":null,"headline":"PeachPay \u003c= 1.120.46 - Cross-Site Request Forgery to Stripe Unlink","id":"CVE-2026-9618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Missing authorization in Reviews and Rating – Docplanner","id":"CVE-2026-9619"},"packages":[],"prev":{"headline":"PostgreSQL Anonymizer: malicious column name allows SQL injection via anon.k_anonymity() function","id":"CVE-2026-9617"},"products":["PeachPay — Payments \u0026 Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI)"],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["peachpay"]},"summary":"Attackers can trick admins into deleting Stripe credentials, disabling payment processing for the store.","url":"https://insights.sbomify.com/CVE-2026-9618/"}