HomeWordPress vulnerabilitiesAdvanced Custom Fields
Advanced Custom Fields vulnerabilities
Advanced Custom Fields has 8 known vulnerabilities in this database. The most recent published record is dated 2 Sep 2026.
- Known vulnerabilities
- 8
- Active installs
- 100,000+
- Latest version
- 0.9.2.7
- Last updated
- 27 Aug 2026
- Most recent
- 2 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Privilege escalation CVE-2026-80467 | High 8.1 | Before 0.9.2.7 | Fixed in 0.9.2.7 | 2 Sep 2026 |
| Authentication bypass CVE-2026-12526 | High 8.1 | Before 0.9.2.7 | Fixed in 0.9.2.7 | 2 Sep 2026 |
| Privilege escalation CVE-2026-8809 | Critical 9.8 | Up to 0.9.2.5 | Fixed in a later version (latest 0.9.2.7) | 28 May 2026 |
| Remote code execution CVE-2025-15463 | Medium 6.5 | Up to 0.9.2.3 | Fixed in a later version (latest 0.9.2.7) | 12 May 2026 |
| Privilege escalation CVE-2025-14533 | Critical 9.8 | Up to 0.9.2.1 | Fixed in a later version (latest 0.9.2.7) | 20 Jan 2026 |
| Remote code execution CVE-2025-13486 | Critical 9.8 | Up to 0.9.1.1 | Fixed in a later version (latest 0.9.2.7) | 3 Dec 2025 |
| Cross-site scripting (XSS) CVE-2023-5292 | Medium 6.4 | Up to 0.8.9.3 | Fixed in a later version (latest 0.9.2.7) | 20 Oct 2023 |
| SQL injection CVE-2021-24865 | High 7.2 | Before 0.8.8.7 | Fixed in 0.8.8.7 | 24 Jan 2022 |
Read the published descriptions
- CVE-2026-80467, 2 Sep 2026
- The Advanced Custom Fields: Extended WordPress plugin before 0.9.2.7 does not restrict the role submitted through its front-end user forms to the roles the form actually offers, and its safeguard against privileged roles is incomplete, allowing unauthenticated visitors to register an account with elevated capabilities and then escalate it to administrator. CVE record
- CVE-2026-12526, 2 Sep 2026
- The Advanced Custom Fields: Extended WordPress plugin before 0.9.2.7 does not verify that the requester is authorized to edit the targeted user account in the update-user action of its front-end Forms module; it only checks a capability when the submitted role is administrator or super_admin. On a site that exposes a publicly reachable front-end form whose user-update action targets an existing administrator (a fixed target, or one mapped to a visitor-submitted field) and maps the password to a visitor-submitted field, an unauthenticated visitor can overwrite that administrator's password and take over the account. The default target is the submitting user, so exploitation depends on the form being configured to target another account. CVE record
- CVE-2026-8809, 28 May 2026
- The Advanced Custom Fields: Extended plugin for WordPress is vulnerable to Privilege Escalation via Validation Bypass in all versions up to and including 0.9.2.5. The vulnerability exists due to the after_validate_save_post() function unconditionally trusting the attacker-controlled _acf_post_id POST parameter - with no authentication or integrity verification - to select a cleanup branch that silently discards all validation errors not prefixed with acfe:. This makes it possible for unauthenticated attackers to suppress both the role allow-list validation error added by acfe_field_user_roles::validate_front_value() and the administrator-role capability guard error added by acfe_module_form_action_user::validate_action(), causing wp_insert_user() to execute with an attacker-supplied administrator role argument and resulting in the creation of a new administrator-level user account. Exploitation requires the target site to expose a public ACFE frontend form configured with a Create User action that maps a role field. CVE record
- CVE-2025-15463, 12 May 2026
- The The Advanced Custom Fields: Extended plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 0.9.2.3. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. CVE record
- CVE-2025-14533, 20 Jan 2026
- The Advanced Custom Fields: Extended plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 0.9.2.1. This is due to the 'insert_user' function not restricting the roles with which a user can register. This makes it possible for unauthenticated attackers to supply the 'administrator' role during registration and gain administrator access to the site. Note: The vulnerability can only be exploited if 'role' is mapped to the custom field. CVE record
- CVE-2025-13486, 3 Dec 2025
- The Advanced Custom Fields: Extended plugin for WordPress is vulnerable to Remote Code Execution in versions 0.9.0.5 through 0.9.1.1 via the prepare_form() function. This is due to the function accepting user input and then passing that through call_user_func_array(). This makes it possible for unauthenticated attackers to execute arbitrary code on the server, which can be leveraged to inject backdoors or create new administrative user accounts. CVE record
- CVE-2023-5292, 20 Oct 2023
- The Advanced Custom Fields: Extended plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'acfe_form' shortcode in versions up to, and including, 0.8.9.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2021-24865, 24 Jan 2022
- The Advanced Custom Fields: Extended WordPress plugin before 0.8.8.7 does not validate the order and orderby parameters before using them in a SQL statement, leading to a SQL Injection issue CVE record
What to do if you run Advanced Custom Fields
If you run Advanced Custom Fields, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Advanced Custom Fields vulnerabilities
Free. We email you when a new vulnerability is published for Advanced Custom Fields, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.