CVE-2024-0629
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 2Checkout Payment Gateway for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the sniff_ins function in all versions up to, and including, 6.2. This makes it possible for unauthenticated attackers to make changes to orders and mark them 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 2Checkout Payment Gateway plugin for WooCommerce lacks authorization checks on the sniff_ins function, allowing unauthenticated attackers to call this function directly and modify order data, specifically to mark orders as paid without proper payment processing.
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.
-
Identify if 2Checkout Payment Gateway plugin is installedCheck the WordPress plugins directory at wp-content/plugins/ for a folder containing '2checkout' or '2Checkout' in the name. Look for the main plugin PHP file and read the plugin header for the Version field.Affected if The plugin folder exists and the Version header shows a version lower than 6.3, or the version cannot be determined.
-
Locate the vulnerable sniff_ins functionSearch the plugin files for the function definition 'function sniff_ins' using grep, grep -r 'function sniff_ins' /path/to/wp-content/plugins/2checkout/, or a file search in the plugin folder.Affected if The function sniff_ins is found defined in the plugin files.
-
Verify the sniff_ins function lacks authorization checksOpen the file containing sniff_ins and examine the function code. Look for capability checks (current_user_can), nonce verification, or authentication gates before any order modification logic.Affected if The sniff_ins function contains order modification logic (such as updating post meta, order status, or payment status) without any current_user_can() checks or nonce validation at the function start.
-
Check for unauthorized order status modificationsReview WooCommerce order notes and order history in wp-admin > WooCommerce > Orders. Look for suspicious 'pending' to 'completed' or 'processing' transitions, especially in bulk or at unusual times, or query the wp_postmeta table for meta_key '_paid_date' set without corresponding payment gateway records.Affected if Orders show completion status changes without corresponding payment transaction records from the 2Checkout gateway.
-
Inspect server access logs for exploit attemptsSearch web server access logs (Apache, Nginx) for requests to the plugin endpoint containing 'sniff_ins', '2checkout', or order ID parameters from unauthenticated IP addresses. Example: grep -i 'sniff_ins' /var/log/apache2/access.logAffected if HTTP requests to sniff_ins or similar endpoints are logged from unauthenticated sources, especially in high volume or with sequential order IDs.
You are affected if the 2Checkout Payment Gateway plugin is installed with a version before 6.3 AND the sniff_ins function exists without authorization checks in the code, or if you find evidence of orders marked as paid without valid payment transactions.
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 to version 6.3 or later when available; until then, consider restricting access to the vulnerable endpoint via server-side rules or deploying a WAF rule to block unauthorized order modification requests.
latest available version (after 6.2)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the '2Checkout Payment Gateway for WooCommerce' plugin
- Check if an update is available and update to the latest version
- Alternatively, navigate to Dashboard > Updates and update the plugin from there
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0629 — 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-0629 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