WordPress plugin · wc-fields-factory
Is WC Fields Factory safe?
A flaw affects the current version.
The newest release on wordpress.org, 4.1.12, is inside the affected range of CVE-2026-39727, so there may be no fix yet. Check the changelog; if it doesn’t mention the fix, deactivate it until it does.
- Flaws on record
- 4
- High or critical
- 2
- Exploited
- none
- Current version
- 4.1.12
- Last updated
- Sep 17, 2026
- Active installs
- 7,000+
Every recorded flaw
- Oct 6, 2026Subscriber Cross Site Scripting (XSS) in WC Fields Factory <= 4.1.12 versions.CVE-2026-39727 · affects up to 4.1.12 · reported by PatchstackMedium 6.5
- Sep 23, 2026WC Fields Factory: Does not properly restrict access to its field-management AJAX actionCVE-2026-93508 · fixed in 4.1.11 · reported by WPScanHigh 8.1
- Sep 23, 2026WC Fields Factory: Does not properly restrict access toCVE-2026-93507 · fixed in 4.1.11 · reported by WPScanLow 3.3
- Apr 17, 2023WC Fields Factory: Does not properly sanitise and escape a parameter before using it in a SQL statementCVE-2023-0277 · affects up to 4.1.5 · reported by WPScanHigh 7.2
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.