CVE-2024-1688
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 Woo Total Sales plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the get_orders_archive() function in all versions up to, and including, 3.1.4. This makes it possible for unauthenticated attackers to retrieve sales reports for the store.
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 Woo Total Sales WordPress plugin has a broken access control vulnerability in the get_orders_archive() function, which lacks a capability check. This allows unauthenticated attackers to access the function and retrieve sensitive sales reports from the store, exposing business-critical data.
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.
-
Confirm Woo Total Sales plugin is installedNavigate to WordPress admin > Plugins and look for 'Woo Total Sales' in the installed plugins list, or check the /wp-content/plugins/ directory for the woo-total-sales folderAffected if The plugin is installed and active
-
Identify the installed plugin versionIn WordPress admin > Plugins > Woo Total Sales, click on the plugin name to view details and note the version number, or check the main plugin file header for the 'Version' tagAffected if The version is lower than 3.1.5 (the patched version)
-
Test unauthenticated access to the vulnerable endpointSend a direct HTTP request to the AJAX endpoint that calls get_orders_archive() - typically something like /wp-admin/admin-ajax.php?action=get_orders_archive or /wp-json/wts/v1/orders - using a tool like curl without providing any authentication cookiesAffected if The endpoint returns sales report data (order details, revenue figures, customer information) without requiring login credentials
-
Inspect the get_orders_archive function codeAccess the plugin files via FTP or file manager, locate the main plugin PHP file (usuallywoo-total-sales.php or similar), search for the function get_orders_archive and examine whether it contains a capability check like current_user_can() before returning dataAffected if The function lacks a current_user_can() or similar authorization check before processing and returning sales data
You are affected if the Woo Total Sales plugin is installed with a version before 3.1.5 AND the get_orders_archive() endpoint is accessible without authentication, returning sensitive sales data.
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 Woo Total Sales plugin to version 3.1.5 or later which includes the missing capability check. If no patched version is available, consider removing the plugin or implementing WAF rules to block unauthorized access to the vulnerable endpoint.
- 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-1688 — 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-1688 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