Skip to main content
EPSS 0.1%top 99%

CVE-2026-89411: CWE-345 Insufficient Verification of Data Authenticity in Paymattic

0
Medium
VulnerabilityCVE-2026-89411cvecve-2026-89411cwe-345
Published: 09/28/2026 (09/28/2026, 06:19:21 UTC)
Source: CVE Database V5
Product: Paymattic

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.

CVSS v3.1

Score 5.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected software

Paymattic

Affected versions
>=4.6.20 <4.6.26

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/28/2026, 07:02:59 UTC

Technical Analysis

CVE-2026-89411 is an insufficient verification of data authenticity vulnerability (CWE-345) in the Paymattic WordPress plugin. Specifically, versions from 4.6.20 up to but not including 4.6.26 fail to verify that a confirmed Stripe payment corresponds to the intended order. This flaw allows unauthenticated attackers to mark arbitrary pending orders as paid by confirming a smaller payment against them, potentially leading to unauthorized order fulfillment or accounting inconsistencies.

Potential Impact

The vulnerability allows unauthenticated attackers to manipulate order payment status by associating their own smaller Stripe payments with arbitrary pending orders. This can result in unauthorized marking of orders as paid, impacting the integrity of order processing and potentially causing financial or operational discrepancies. There is no direct confidentiality or availability impact reported.

Mitigation Recommendations

A fix is available in Paymattic version 4.6.26 and later. Users should upgrade to version 4.6.26 or newer to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2026-09-11T16:27:21.951Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6aba0dbef7a7c541064c3352

Added to database: 09/28/2026, 06:48:30 UTC

Last enriched: 09/28/2026, 07:02:59 UTC

Last updated: 09/29/2026, 02:53:42 UTC

Views: 17

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses