Unauthenticated access to improperly constrained functionality
Published Jul 13, 2026 · Updated Jul 13, 2026
Improper quantity validation in WPDeveloper Better Payment 2.2.0 and earlier allows remote attackers to access constrained functionality. Patchstack and WPDeveloper have not published the affected function or how a quantity input defeats its access constraints. No authentication or user interaction is required, but the accessible functionality and resulting data changes or service interruption remain undisclosed.
Summary
What happened
Improper quantity validation in WPDeveloper Better Payment 2.2.0 and earlier allows remote attackers to access constrained functionality. Patchstack and WPDeveloper have not published the affected function or how a quantity input defeats its access constraints. No authentication or user interaction is required, but the accessible functionality and resulting data changes or service interruption remain undisclosed.
The record
- CVE
- CVE-2026-57364
- Published
- Jul 13, 2026
- Updated
- Jul 13, 2026
- Vendor
- ReviewX Team
- Product
- Better Payment
- Classifications
- CWE-1284, CAPEC-1
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2026CVE publishedPublication date reported by the CVE source.
- Jul 13, 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=0 <=2.2.0 changes=[{"at":"2.2.1","status":"unaffected"}]
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