dbcve.org
Fancy Product DesignerWordPress extension · Radykal

CVE-2021-4335

MEDIUM · 6.3 CVSS v3.1 Published 2023-10-20
Fix available
A fix is available. Upgrade to 4.7.0 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Fancy Product Designer plugin for WordPress is vulnerable to unauthorized access to data and modification of plugin settings due to a missing capability check on multiple AJAX functions in versions up to, and including, 4.6.9. This makes it possible for authenticated attackers with subscriber-level permissions to modify plugin settings, including retrieving arbitrary order information or creating/updating/deleting products, orders, or other sensitive information not associated with their own account.

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 confidence

The Fancy Product Designer WordPress plugin has multiple AJAX functions lacking proper capability checks. Authenticated users with subscriber-level permissions (the lowest privilege role) can access these functions to retrieve arbitrary order information and create/update/delete products, orders, and plugin settings not associated with their account.

MitigationUpdate to version 4.7.0 or later which implements proper capability checks on AJAX endpoints. Alternatively, add current_user_can() verification to all AJAX handlers before processing requests.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Fancy Product DesignerWordPress extension
Affected:< 4.7.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checks

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

  1. Confirm Fancy Product Designer plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Fancy Product Designer' by Radykal in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active (inactive plugins do not expose AJAX handlers)
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin name or view the plugin files. Open the main plugin file (usually fancy-product-designer/fancy-product-designer.php) and locate the 'Version' header comment or a $version variable definition.
    Affected if Version is less than 4.7.0 (vulnerable versions)
  3. Verify AJAX endpoint accessibility
    Check if the plugin registers AJAX actions. Look in the plugin code for add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...') calls. Test by accessing /wp-admin/admin-ajax.php?action=fpd_admin&request=get_orders (or similar plugin-specific AJAX actions found in the code).
    Affected if AJAX endpoints respond to requests without requiring higher privileges than subscriber
  4. Inspect AJAX handler capability checks
    Examine the PHP functions handling AJAX requests (e.g., get_orders, save_product, update_order). Look for current_user_can() or similar WordPress capability checks at the beginning of each handler function.
    Affected if AJAX handlers do NOT contain current_user_can() calls, or the capability required is too low (e.g., 'read' instead of 'manage_options' or 'edit_orders')

You are affected if the Fancy Product Designer plugin is active, version is below 4.7.0, and AJAX endpoints can be accessed by authenticated users with subscriber-level permissions without proper capability verification.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.7.0 or later
Fixed in 4.7.0
Interim mitigation

Update to version 4.7.0 or later which implements proper capability checks on AJAX endpoints. Alternatively, add current_user_can() verification to all AJAX handlers before processing requests.

Recommended fix High confidence

Fancy Product Designer version 4.7.0 or later

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins section
  3. Locate Fancy Product Designer in the installed plugins list
  4. Click 'Update Now' to update the plugin to the latest version (4.7.0 or later)
  5. Verify the plugin updated successfully by checking the installed version
  6. Confirm that the plugin functionality works correctly on your site
  7. Ensure that user role permissions are appropriately configured in WordPress

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

Fix this in Fancy Product Designer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-4335 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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