dbcve.org
Fancy Product DesignerWordPress extension · Radykal

CVE-2021-4334

HIGH · 8.8 CVSS v3.1 Published 2023-10-20
Fix available
A fix is available. Upgrade to 4.7.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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 modification of site options due to a missing capability check on the fpd_update_options function in versions up to, and including, 4.6.9. This makes it possible for authenticated attackers with subscriber-level permissions to modify site options, including setting the default role to administrator which can allow privilege escalation.

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 a missing capability check in the fpd_update_options function, allowing any authenticated user with subscriber-level permissions to modify arbitrary site options. This IDOR vulnerability enables privilege escalation by changing the default user role to administrator.

MitigationUpdate to version 4.7.0 or later which adds proper capability validation; until then, disable the plugin or restrict user registration.

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
High
Integrity
High
Availability
High

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

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 plugin is installed
    Navigate to WP Admin > Plugins and check if 'Fancy Product Designer' by Radykal is installed and active
    Affected if Plugin is installed and active
  2. Identify installed version
    In WP Admin > Plugins, find Fancy Product Designer and view the version number listed under the plugin name. Compare against the affected range of < 4.7.0
    Affected if Installed version is below 4.7.0
  3. Check if user registration is enabled
    Go to WP Admin > Settings > General and find 'Membership: Anyone can register' - verify if the checkbox is checked
    Affected if User registration is enabled and new subscriber accounts can be created
  4. Check default user role setting
    Go to WP Admin > Settings > General and find 'New User Default Role' - this is the role an attacker would attempt to change to administrator
    Affected if The default role setting exists (attacker would target changing this value)
  5. Audit existing subscriber accounts
    Go to WP Admin > Users and filter or search for users with 'Subscriber' role
    Affected if Any subscriber-level accounts exist in the system

A user is affected if the Fancy Product Designer plugin version is below 4.7.0 AND user registration is enabled OR subscriber accounts already exist, allowing privilege escalation via the fpd_update_options function.

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 adds proper capability validation; until then, disable the plugin or restrict user registration.

Recommended fix High confidence

Fancy Product Designer 4.7.0

  1. 1. Back up your WordPress site before making any changes
  2. 2. Log in to the WordPress admin dashboard
  3. 3. Navigate to Plugins > Installed Plugins
  4. 4. Locate Fancy Product Designer in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.7.0
  6. 6. Alternatively, you can manually upload version 4.7.0 of the plugin from the WordPress repository or your purchase source
  7. 7. After updating, verify the plugin version is 4.7.0 or higher under Plugins > Installed Plugins
  8. 8. Test that the Fancy Product Designer functionality works correctly

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

Fix this in Fancy Product Designer 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 the upgrade done

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-2021-4334 — 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-4334 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