Stripe Payments: A security weakness
Stripe Payments is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 2.0.98.
- Component
- Stripe Payments
- Plugin slug
stripe-payments- Affected
- n/a through 2.0.98
- Safe version
2.0.99- Published
- Jun 15, 2026
This CVE was published Jun 15, 2026 and is one of 5 known issues for this plugin.
Update, patch or deactivate.
Update Stripe Payments to 2.0.99 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
Unauthenticated Bypass Vulnerability in Stripe Payments <= 2.0.98 versions.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N