WordPress plugin · add-fields-to-checkout-page-woocommerce
Is Custom WooCommerce Checkout Fields Editor safe?
A flaw affects the current version.
The newest release on wordpress.org, 1.3.4, is inside the affected range of CVE-2025-58799, 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
- 0
- Exploited
- none
- Current version
- 1.3.4
- Last updated
- Jan 1, 2025
- Active installs
- 2,000+
Every recorded flaw
- Sep 5, 2025Custom WooCommerce Checkout Fields Editor: Cross-Site Request Forgery (CSRF)CVE-2025-58799 · affects up to 1.3.4 · reported by PatchstackMedium 4.3
- May 14, 2024Custom WooCommerce Checkout Fields Editor: Missing AuthorizationCVE-2024-33956 · affects up to 1.3.0 · reported by PatchstackMedium 4.3
- Mar 29, 2024Custom WooCommerce Checkout Fields Editor: Cross-Site Request Forgery (CSRF)CVE-2024-30518 · affects up to 1.3.0 · reported by PatchstackMedium 4.3
- Mar 22, 2024Custom WooCommerce Checkout Fields Editor: Stored Cross-Site ScriptingCVE-2024-1697 · affects up to 1.3.1 · reported by WordfenceMedium 6.4
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.