Unauthenticated payment status tampering via unchecked submission ID
Published Apr 16, 2026 · Updated Apr 16, 2026
IDOR in the Stripe SCA endpoint in WPManageNinja Fluent Forms 6.1.21 allows remote attackers to alter pending submission payment status. The AJAX handler accepts a user-controlled submission_id and updates the referenced submission without authorization or ownership validation. No account or user interaction is required; knowledge or a guess of a pending submission ID is enough to set its payment status to failed.
Summary
What happened
IDOR in the Stripe SCA endpoint in WPManageNinja Fluent Forms 6.1.21 allows remote attackers to alter pending submission payment status. The AJAX handler accepts a user-controlled submission_id and updates the referenced submission without authorization or ownership validation. No account or user interaction is required; knowledge or a guess of a pending submission ID is enough to set its payment status to failed.
The record
- CVE
- CVE-2026-4160
- Published
- Apr 16, 2026
- Updated
- Apr 16, 2026
- Vendor
- Mahmudul Hasan Arif
- Product
- Fluent Forms
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2026CVE publishedPublication date reported by the CVE source.
- Apr 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.1.21
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo