CVE-2025-58634
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 · uneditedMissing Authorization vulnerability in peachpay PeachPay Payments peachpay-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PeachPay Payments: from n/a through <= 1.117.4.
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 confidenceThis is a missing authorization vulnerability in the PeachPay Payments plugin for WooCommerce that allows attackers to exploit incorrectly configured access control security levels. The vulnerability stems from improper or missing authorization checks on certain functionality or sensitive data within the plugin.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Verify PeachPay plugin versionGo to WordPress admin > Plugins > locate PeachPay Payments plugin and check the installed version number against the affected range (versions prior to 1.117.4)Affected if The installed version is below 1.117.4
-
Inspect plugin access control settingsNavigate to WooCommerce > Settings > PeachPay (or the plugin settings page if accessible) and review any access control, permission, or role configuration options for missing or weak authorization settingsAffected if Authorization settings are absent, misconfigured, or allow lower-privileged users to access sensitive functionality
-
Check for unauthenticated or low-privilege API endpointsReview the plugin files (wp-content/plugins/peachpay-for-woocommerce/) for AJAX actions, REST API routes, or admin-ajax.php hooks that may lack capability checks or nonce validation on sensitive operationsAffected if Sensitive actions are reachable without proper capability checks or authorization verification
-
Audit user role permissionsIn WordPress admin > Users > Roles, examine if PeachPay creates custom roles or modifies capabilities in a way that grants sensitive payment or configuration actions to roles that should not have such accessAffected if Users with low-privileged roles (such as Subscriber or Customer) can access or modify payment-related settings or data
The environment is affected if the PeachPay plugin version is below 1.117.4 AND sensitive functionality within the plugin is accessible without proper authorization checks.
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 PeachPay Payments plugin to the latest patched version beyond 1.117.4. If no patch is available, review and remediate access control configurations within the plugin to ensure all sensitive actions and data are properly protected by authorization checks.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58634 — 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-2025-58634 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