Missing AuthorizationWeakness · CWE-862

CVE-2024-3608

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-09

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The Product Designer plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the product_designer_ajax_delete_attach_id() function in all versions up to, and including, 1.0.33. This makes it possible for unauthenticated attackers to delete arbitrary attachments. CVE-2024-38726 appears to be a duplicate of this issue.

Technical summary

dbcve analysis · high confidence

The Product Designer WordPress plugin has a missing capability check on the product_designer_ajax_delete_attach_id() function, allowing unauthenticated attackers to delete arbitrary attachments from the WordPress site. This is an Insecure Direct Object Reference (IDOR) combined with improper authorization on an AJAX endpoint.

MitigationUpdate the Product Designer plugin to version 1.0.34 or later, which should include proper capability checks. Until a patch is available, consider disabling the plugin or restricting access to the affected AJAX endpoint via web server configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Product Designer plugin is installed

Go to WordPress Admin > Plugins and look for 'Product Designer' in the installed plugins list, or check the /wp-content/plugins/ directory for a product-designer folder

Affected if The plugin is installed and active
Check installed plugin version

In WordPress Admin > Plugins, find Product Designer and note the version number displayed. Compare it to version 1.0.34 (the patched release)

Affected if Version is lower than 1.0.34 or the version cannot be determined (plugin may be unpatched)
Test AJAX endpoint accessibility

Send a POST request to /wp-admin/admin-ajax.php with action=product_designer_ajax_delete_attach_id and a valid attachment ID parameter, without providing authentication credentials

Affected if The request returns a successful response (HTTP 200) without requiring login or capability verification - this indicates the vulnerability is present
Review WordPress access logs

Examine server access logs for repeated POST requests to admin-ajax.php?action=product_designer_ajax_delete_attach_id from unauthorized IP addresses

Affected if Such requests appear in the logs, indicating possible exploitation attempts

A user is affected if the Product Designer plugin version is below 1.0.34 AND the AJAX endpoint at admin-ajax.php accepts unauthenticated delete requests for attachments.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the Product Designer plugin to version 1.0.34 or later, which should include proper capability checks. Until a patch is available, consider disabling the plugin or restricting access to the affected AJAX endpoint via web server configuration.

Recommended fix Moderate confidence

Any version after 1.0.33 (check WordPress Plugin Repository for latest stable release)

Log in to the WordPress admin dashboard
Navigate to Plugins > Installed Plugins
Locate the 'Product Designer' plugin
Check if an update is available and install the latest version (any version after 1.0.33 contains the fix)
Alternatively, download the updated plugin from the WordPress Plugin Repository and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

Get help mitigating

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 locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-3608 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3608 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-3608?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.6%

Remediation

Need this fixed?

Have this fixed 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-3608 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References