{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9189 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9189 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9189 is a medium-severity vulnerability in scottpaterson Contact Form 7 – PayPal \u0026 Stripe Add-on, published on 29 May 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-2026-9189 and fix it if it is affected.\n\nWhat it is: CVE-2026-9189 is a medium-severity vulnerability in scottpaterson Contact Form 7 – PayPal \u0026 Stripe Add-on, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9189 in the wild and no public exploit code.\n\nAffected product: scottpaterson Contact Form 7 – PayPal \u0026 Stripe Add-on. 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-9189/ (Markdown: https://insights.sbomify.com/CVE-2026-9189/index.md)","id":"CVE-2026-9189","markdown":"https://insights.sbomify.com/CVE-2026-9189/index.md","name":"CVE-2026-9189","record":{"aliases":["GHSA-vr4h-g9wj-2p4g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress payment plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass payment verification to mark high-value orders as paid, resulting in unauthorized purchases.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"The Contact Form 7 – PayPal \u0026 Stripe Add-on plugin for WordPress is vulnerable to Payment Bypass via Insufficient Verification of Data Authenticity in all versions up to, and including, 2.4.9. Although `cf7pp_paypal_ipn_handler()` correctly validates IPN authenticity by posting back to PayPal with `cmd=_notify-validate`, it fails to compare the IPN payload's `mc_gross` (payment amount), `mc_currency`, or `receiver_email` fields against the corresponding stored order values before passing the attacker-controlled `invoice` field directly to `cf7pp_complete_payment()`, which marks the order completed after only an integer cast with no amount verification. This makes it possible for unauthenticated attackers to mark arbitrary high-value pending orders as fully paid by making a minimal real PayPal payment and crafting an IPN whose `invoice` parameter references the targeted order, effectively completing purchases without tendering the required payment amount.","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":"Business logic in Contact Form 7 – PayPal \u0026 Stripe Add-on","id":"CVE-2026-9189","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"HTTP request smuggling in Progress MarkLogic Server","id":"CVE-2026-9190"},"packages":[],"prev":{"headline":"Missing authorization in Appointment Bookings for Zoom GoogleMeet and more – Wappointment","id":"CVE-2026-9188"},"products":["Contact Form 7 – PayPal \u0026 Stripe Add-on"],"published":"2026-05-29","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["scottpaterson"]},"summary":"Unauthenticated attackers can bypass payment verification to mark high-value orders as paid, resulting in unauthorized purchases.","url":"https://insights.sbomify.com/CVE-2026-9189/"}