CVE-2024-12265
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 · uneditedThe Web3 Crypto Payments by DePay for WooCommerce plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the /wp-json/depay/wc/debug REST API endpoint in all versions up to, and including, 2.12.17. This makes it possible for unauthenticated attackers to retrieve debug infromation.
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 · high confidenceThe Web3 Crypto Payments by DePay plugin for WordPress exposes a debug REST API endpoint at /wp-json/depay/wc/debug without any capability verification. This allows any unauthenticated user on the network to access potentially sensitive debug information, constituting a Broken Access Control vulnerability in the WordPress REST API.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 DePay plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Web3 Crypto Payments by DePay' or check the plugin version via wp-content/plugins/depay-payments/ directory or WordPress REST API at /wp-json/wp/v2/pluginsAffected if The plugin is installed and active in WordPress
-
Check plugin version against fixed releaseCompare the installed plugin version to version 2.12.18. If you have CLI access, check wp-content/plugins/depay-payments/readme.txt or the plugin header in the main PHP file for the Version fieldAffected if The installed version is lower than 2.12.18 (the version that added proper capability checking)
-
Test unauthenticated access to debug endpointSend a GET request to https://your-site.com/wp-json/depay/wc/debug using curl or a browser while NOT logged in. No authentication headers or cookies should be providedAffected if The endpoint returns an HTTP 200 response with debug information instead of requiring authentication or returning HTTP 401/403
-
Inspect response for sensitive informationExamine the JSON response from the /wp-json/depay/wc/debug endpoint. Look for debug data such as configuration details, API keys, transaction data, internal paths, or other potentially sensitive system informationAffected if The response contains debug output, configuration details, or sensitive data accessible without authentication
If the DePay plugin versions below 2.12.18 are installed and the /wp-json/depay/wc/debug endpoint returns debug information without requiring authentication, the environment is affected by this CVE.
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 plugin to version 2.12.18 or later which adds proper capability checking to the debug REST endpoint. Until then, consider disabling the debug functionality or restricting access to the REST API.
- 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-2024-12265 — 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-2024-12265 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