Fancy Product DesignerWordPress extension · Radykal
CVE-2021-4096
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 Fancy Product Designer plugin for WordPress is vulnerable to Cross-Site Request Forgery via the FPD_Admin_Import class that makes it possible for attackers to upload malicious files that could be used to gain webshell access to a server in versions up to, and including, 4.7.5.
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 Fancy Product Designer WordPress plugin contains a CSRF vulnerability in the FPD_Admin_Import class that allows attackers to trick authenticated administrators into uploading malicious files. Successful exploitation enables remote code execution via webshell access to the server.
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
<= 4.7.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Fancy Product Designer is installedCheck your WordPress plugins directory (wp-content/plugins) for the 'fancy-product-designer' folder, or view the plugin in WordPress admin under Plugins > Installed PluginsAffected if The plugin folder 'fancy-product-designer' exists in your plugins directory
-
Identify the installed plugin versionOpen the main plugin file (fancy-product-designer.php) and look for the version comment/constant at the top, or check the version displayed in WordPress admin plugin listAffected if The version number shown is 4.7.5 or lower (e.g., 4.7.5, 4.7.4, 4.6.x, etc.)
-
Verify the vulnerable import class is presentSearch the plugin files for the FPD_Admin_Import class definition, typically in admin/class-fpd-admin-import.php or similar within the plugin structureAffected if The FPD_Admin_Import class exists and contains file upload handling code without visible CSRF token validation
-
Inspect uploaded files for suspicious PHPCheck the wp-content/uploads/fpd directory (or similar product upload folders) for unfamiliar .php files that were not deliberately uploaded by an administratorAffected if Unexpected PHP files exist in the uploads directory that you did not intentionally place there
-
Review server access logs for import endpoint activityExamine your web server access logs for POST requests to endpoints containing 'import' or 'upload' actions related to fancy-product-designer, particularly from admin sessionsAffected if POST requests to import functionality appear in logs without proper CSRF token validation in the request parameters
You are affected if the Fancy Product Designer plugin version is 4.7.5 or lower AND the FPD_Admin_Import class is present and accessible to authenticated administrators.
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.
dbcve · scopedUpdate the Fancy Product Designer plugin to the latest version beyond 4.7.5, which should contain proper CSRF validation and file upload restrictions. Consider implementing additional server-side CSRF token validation as a defense-in-depth measure.
Fancy Product Designer 4.7.6 or latest stable release
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate Fancy Product Designer
- Check if current version is 4.7.5 or lower
- If vulnerable, click 'Update Now' to update to the latest version (4.7.6 or higher)
- Alternatively, download the latest version from the WordPress plugin repository or from support.fancyproductdesigner.com
- Backup the site before performing any updates
- Verify the update was successful and the new version is active
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
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 locallyCheck whether your project pulls in CVE-2021-4096 — 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-2021-4096 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