Custom WooCommerce Checkout Fields Editor
add-fields-to-checkout-page-woocommerce · plugin
Known security vulnerabilities for Custom WooCommerce Checkout Fields Editor. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
2 exploitable without logging in · 1 with no official fix seen · latest Sep 5, 2025
Before you install
Do not install
- 1 record shows no fix in the latest wordpress.org release.
- 1 record needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 1.3.4 · last updated Jan 1, 2025 · 2K+ installs
wordpress.org status checked on Oct 30, 2026
Vulnerabilities
- Medium 5.4
CVE-2024-1697subscriber+≤ 1.3.1
Custom WooCommerce Checkout Fields Editor <= 1.3.1 - Authenticated (Subscriber+) Stored Cross-Site Scripting
- Medium 4.3
CVE-2025-58799unauthenticated · needs a clickno fix seen
WordPress Custom WooCommerce Checkout Fields Editor Plugin <= 1.3.4 - Cross Site Request Forgery (CSRF) Vulnerability
- Medium 4.3
CVE-2024-30518unauthenticated · needs a click≤ 1.3.0
WordPress Custom WooCommerce Checkout Fields Editor plugin <= 1.3.0 - Cross Site Request Forgery (CSRF) vulnerability
- Medium 4.3
CVE-2024-33956login required≤ 1.3.0
WordPress Custom WooCommerce Checkout Fields Editor plugin <= 1.3.0 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (1.3.4) as affected.