CVE-2026-57364
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Validation of Specified Quantity in Input vulnerability in WPDeveloper Better Payment – Instant Payments, Donations, Fundraising with Subscriptions & More better-payment allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Better Payment – Instant Payments, Donations, Fundraising with Subscriptions & More: from n/a through <= 2.2.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Better Payment WordPress plugin through version 2.2.0 contains an input validation vulnerability where certain quantity-related fields are not properly validated, combined with missing Access Control List (ACL) constraints on specific functionality. This allows authenticated attackers to bypass intended access restrictions and manipulate payment/donation quantities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Better Payment plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Better Payment. The version number is displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/better-payment/better-payment.php for the 'Version' comment.Affected if The installed version is 2.2.0 or lower.
-
Verify payment/donation forms are activeNavigate to Better Payment settings or form builder in the WordPress admin panel. Check if any payment forms, donation widgets, or payment buttons are published and active on the site.Affected if Active payment or donation forms exist that accept user input for quantity values.
-
Inspect quantity input fields in payment formsView the source of any published payment form or use the form builder to examine field configurations. Look for fields related to quantity, amount, or donation quantity that accept user-supplied values.Affected if Quantity fields accept numeric input without proper validation constraints.
-
Review user role permissions for payment actionsGo to WordPress Users > Roles or Better Payment role settings. Examine which user roles (subscriber, contributor, author, editor, etc.) have permission to create, edit, or submit payment forms and process transactions.Affected if Lower-privileged users (such as subscribers or unauthenticated users) can access or manipulate payment quantity parameters.
-
Test for ACL bypass on quantity parametersSubmit a test payment request with manipulated quantity parameters (e.g., negative values, extreme values, or modified form data) using a low-privilege account or via direct API/form submission. Observe if the system accepts values that should be restricted by access controls.Affected if The system accepts quantity values that bypass intended access restrictions or validation rules.
You are affected if the Better Payment plugin version is 2.2.0 or lower AND payment/donation forms with quantity fields are active and accessible to authenticated users without proper ACL enforcement.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Better Payment plugin to the latest version and audit user roles/permissions to ensure ACLs are properly enforcing access controls on payment-related functionality.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data