CVE-2026-89411

Paymattic < 4.6.26 - Unauthenticated Payment Bypass via Unbound Stripe PaymentIntent

MEDIUM

5.3

CVSS Score

Published: September 28, 2026 at 06:19 AM UTC

Updated: September 28, 2026 at 04:38 PM UTC

1 product affected across 1 vendorPaymattic

Using Paymattic by Unknown?

Get instant alerts when new vulnerabilities affect Paymattic - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.3

Exploit prediction

EPSS 0.1%

SSVC

No known exploit

Description

The Paymattic WordPress plugin from 4.6.20 before 4.6.26 does not verify that a confirmed Stripe payment belongs to the order it is applied to, allowing unauthenticated users to mark an arbitrary pending order as paid by confirming a smaller payment of their own against it.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Paymattic · Wpmanageninjawordpress-plugin

60%

4.6.20 ≤ v < 4.6.264.6.20

Affected range stops below 4.6.26, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

ExploitVDB EntryTechnical Description

Source: cverecord

https://wpscan.com/vulnerability/240a0440-7892-4c03-b282-2fdb6f086bb6/

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMWPScan

Vector?

Quick Info

StatusDEFERRED

CWE

CWE-345

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card