Skip to content
Fencer Vulns
critical 9.8

CVE-2021-24370 in the critical feed json

Fancy Product Designer < 4.6.9 - Unauthenticated Arbitrary File Upload and RCE

published 2021-06-21 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-11283

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
47.4%
EPSS 47.4% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known, plus a Nuclei check

Summary

The Fancy Product Designer WordPress plugin before 4.6.9 allows unauthenticated attackers to upload arbitrary files, resulting in remote code execution.

Patch / fix

  • radykal fancy_product_designer 4.6.9

Exploit prediction

47.37% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Nuclei template WordPress Fancy Product Designer <4.6.9 - Arbitrary File Upload nuclei detection template
  • wpscan.com https://wpscan.com/vulnerability/82c52461-1fdc-41e4-9f51-f9dd84962b38 referenced PoC, tagged "exploit" by a source, unverified
  • wordfence.com https://www.wordfence.com/blog/2021/06/critical-0-day-in-fancy-product-designer-under-active-attack/ referenced PoC, tagged "exploit" by a source, unverified
  • lists.openwall.net https://lists.openwall.net/full-disclosure/2020/11/17/2 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org https://seclists.org/fulldisclosure/2020/Nov/30 referenced PoC, tagged "exploit" by a source, unverified
  • secpod.com https://www.secpod.com/blog/critical-zero-day-flaw-actively-exploited-in-wordpress-fancy-product-designer-plugin/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Unknown Fancy Product Designer

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.