CVE-2024-1732
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 Sharkdropship for AliExpress Dropshipping and Affiliate plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the wads_removeProductFromShop() function in all versions up to, and including, 2.2.4. This makes it possible for unauthenticated attackers to delete arbitrary posts.
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 Sharkdropship WordPress plugin lacks a capability check on the wads_removeProductFromShop() function, allowing unauthenticated attackers to delete any post on the site via an insecure direct object reference. This is a classic IDOR/broken access control vulnerability where the function directly processes deletion requests without verifying user permissions.
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.
-
Verify Sharkdropship plugin is installedNavigate to WordPress admin dashboard > Plugins and locate the Sharkdropship plugin, or check the /wp-content/plugins/ directory for the sharkdropship folderAffected if The plugin is present on the WordPress site
-
Determine installed plugin versionIn Plugins admin page, click on the plugin name to view details, or inspect the main plugin file header in /wp-content/plugins/sharkdropship/ for the Version: fieldAffected if Installed version is lower than 2.2.5 (the patched version)
-
Confirm wads_removeProductFromShop function existsInspect the main plugin PHP file (usually sharkdropship.php) and search for the function wads_removeProductFromShop or look for AJAX/action handlers that call this functionAffected if The vulnerable function exists in the plugin code
-
Check if the deletion endpoint is accessible without authenticationTest accessing the plugin's AJAX endpoint or direct request handler (commonly /wp-admin/admin-ajax.php with action=wads_remove_product or similar) without being logged inAffected if The endpoint responds to unauthenticated requests and accepts a post ID parameter
If the Sharkdropship plugin is installed with a version below 2.2.5 and the deletion function is exposed to unauthenticated users, the site is vulnerable to CVE-2024-1732.
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 to version 2.2.5 or later. If no patched version is available, disable the plugin until a fix is released. Alternatively, restrict access to the affected endpoint at the web server level until patched.
- 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-1732 — 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-1732 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