CVE-2024-1807
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 Product Sort and Display for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the psad_update_product_cat_custom_meta_ajax function in all versions up to, and including, 2.4.1. This makes it possible for unauthenticated attackers to hide product categories.
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 Product Sort and Display for WooCommerce plugin lacks proper authorization checks on the psad_update_product_cat_custom_meta_ajax function, allowing unauthenticated users to modify product category metadata. Attackers can exploit this broken access control vulnerability to hide WooCommerce product categories by sending crafted AJAX requests without any authentication or capability verification.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 the plugin is installedCheck your WordPress plugins directory or the WordPress admin dashboard under Plugins to confirm 'Product Sort and Display for WooCommerce' is installed and active.Affected if The plugin is present and active in your WordPress environment.
-
Identify the installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins and look for the version number listed for 'Product Sort and Display for WooCommerce'. Alternatively, check the plugin's main PHP file or readme.txt for the Version header.Affected if The installed version is lower than 2.4.2.
-
Confirm the vulnerable AJAX endpoint existsCheck if the file wp-content/plugins/product-sort-and-display-for-woocommerce/ contains PHP files with the function 'psad_update_product_cat_custom_meta_ajax' or similar AJAX handlers. Inspect the code to verify the endpoint is registered without capability checks.Affected if The AJAX handler exists and processes requests without verifying user authentication or capabilities.
-
Test unauthenticated AJAX accessSend a crafted request to /wp-admin/admin-ajax.php with action=psad_update_product_cat_custom_meta (or the equivalent action name found in the plugin) without providing any authentication cookies or nonce tokens.Affected if The endpoint accepts and processes the request without requiring authentication.
You are affected if the Product Sort and Display for WooCommerce plugin is installed with a version below 2.4.2 and the AJAX endpoint remains accessible to unauthenticated users.
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.4.2 or later which includes the missing capability check. Until then, consider disabling the plugin or restricting access to the /wp-admin/admin-ajax.php endpoint via server-side rules.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1807 — 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-1807 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