CVE-2024-12004
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 WPC Order Notes for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5.2. This is due to missing or incorrect nonce validation on the ajax_update_order_note() function. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 WPC Order Notes for WooCommerce plugin has a CSRF vulnerability in the ajax_update_order_note() function due to missing nonce validation. This allows unauthenticated attackers to forge requests and inject malicious scripts by tricking administrators into clicking malicious links.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Confirm the WPC Order Notes plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WPC Order Notes for WooCommerce', or check the plugin files in wp-content/plugins/wpc-order-notes/Affected if The plugin is not installed or not active
-
Identify the installed plugin versionIn Plugins list page, click on the plugin name to view details, or open the main plugin file (wpc-order-notes.php) and locate the Version header commentAffected if Version is earlier than 1.5.3 (the fixed version)
-
Verify the ajax_update_order_note function lacks nonce protectionExamine the plugin PHP files, specifically the handler for ajax_update_order_note (usually in includes/class-ajax.php or the main plugin file). Look for wp_verify_nonce(), check_ajax_referer(), or similar nonce validation before processing the request.Affected if No nonce validation function is found before the order note processing logic
-
Confirm the vulnerable endpoint is accessibleCheck that the wp_ajax_wpc_ajax_update_order_note or similar AJAX action is registered and accessible to administrators (or improperly to unauthenticated users)Affected if The AJAX endpoint exists without CSRF protection tokens in the request flow
User is affected if the WPC Order Notes for WooCommerce plugin is installed with a version earlier than 1.5.3 and the ajax_update_order_note function lacks nonce validation.
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 1.5.3 or later which includes proper nonce validation, or manually add wp_verify_nonce() or check_ajax_referer() validation to the ajax_update_order_note() function.
1.5.3 or latest stable version
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WPC Order Notes for WooCommerce in the plugin list
- Check for available updates or verify current version is 1.5.3 or later
- If update available, click Update Now to install version 1.5.3 or the latest stable release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12004 — 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-12004 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