CVE-2024-0626
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 WooCommerce Clover Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the callback_handler function in all versions up to, and including, 1.3.1. This makes it possible for unauthenticated attackers to mark orders as paid.
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 WooCommerce Clover Payment Gateway plugin for WordPress has a missing capability check on the callback_handler function, allowing unauthenticated attackers to arbitrarily mark orders as paid by calling this function directly. This is a direct object reference vulnerability where the plugin trusts external input without proper authorization validation.
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.
-
Check if WooCommerce Clover Payment Gateway plugin is installedIn WordPress admin, go to Plugins and look for 'WooCommerce Clover Payment Gateway', or check the /wp-content/plugins/ directory for a folder named clover-payment-gateway or similarAffected if The plugin folder exists in the plugins directory
-
Verify the installed plugin versionIn WordPress admin > Plugins, click on the plugin to view the version number, or open the main plugin PHP file and look for the 'Version:' header in the plugin comment blockAffected if The version is lower than 1.3.2 (the patched version)
-
Confirm WooCommerce is activeIn WordPress admin > Plugins, verify WooCommerce is installed and activated; this plugin is a WooCommerce payment gateway and requires WooCommerce to functionAffected if WooCommerce is not installed or is deactivated
-
Verify the plugin is activeIn WordPress admin > Plugins, check that WooCommerce Clover Payment Gateway shows as 'Active'Affected if The plugin is activated and processing payments
If the WooCommerce Clover Payment Gateway plugin is installed and active with a version below 1.3.2, the environment is affected by this missing capability check vulnerability.
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.
dbcve · scopedUpdate the plugin to version 1.3.2 or later which adds proper capability checks to the callback_handler function, or implement authorization verification before allowing any order status modifications.
latest version beyond 1.3.1
- 1. Update the WooCommerce Clover Payment Gateway plugin to the latest available version from the WordPress plugin repository
- 2. After updating, verify that the callback_handler function now includes proper capability checks
- 3. Test the payment callback functionality to ensure orders can still be properly marked as paid through legitimate payment processing
- 4. Review user roles and permissions to ensure only authorized users can modify order payment statuses
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0626 — 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-0626 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