Advanced Custom Fields <= 6.3.5 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 6.3.6
- Affected Plugin
- Advanced Custom Fields Pro
- Affected Version
<= 6.3.5- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2024-45429
At a glance
CVE-2024-45429 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Advanced Custom Fields Pro WordPress plugin, affecting versions <= 6.3.5. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 6.3.6; sites on affected versions should update now. Disclosed September 2024, reported by Ryo Sotoyama.
Vulnerability Overview
The Advanced Custom Fields plugin for WordPress is vulnerable to Stored Cross-Site Scripting via field groups in all versions up to, and including, 6.3.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with the 'capability' setting privilege, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Advanced Custom Fields Pro <= 6.3.5 carries this weakness at capability, and reaching it takes any authenticated account. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Advanced Custom Fields Pro the fix is 6.3.6: builds <= 6.3.5 are affected, anything from 6.3.6 onward is not.
Remediation
Update to version 6.3.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Advanced Custom Fields Pro: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Advanced Custom Fields Pro 6.3.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.4CVE-2023-6701: Advanced Custom Fields <= 6.2.4 Stored XSS
CVE-2023-6701 - 6.1CVE-2023-30777: Advanced Custom Fields 5.8.10… Reflected XSS
CVE-2023-30777 - 6.1CVE-2021-24241: Advanced Custom Fields Pro <= 5.9.0 Reflected XSS
CVE-2021-24241 - 4.4CVE-2024-49593: Advanced Custom Fields & Secure Custom Fields <=
CVE-2024-49593
Other vulnerabilities in Advanced Custom Fields Pro
- 9.9CVE-2024-34761: Advanced Custom Fields Pro <= 6.2.9 Code Injection
CVE-2024-34761 - 8.8CVE-2024-34762: Advanced Custom Fields Pro <= 6.2.9 LFI
CVE-2024-34762 - 7.5CVE-2021-20865: Advanced Custom Fields <= 5.10 Information Disclosure
CVE-2021-20865 - 6.5CVE-2022-23183: Advanced Custom Fields <= 5.12 Information Disclosure
CVE-2022-23183 - 6.5CVE-2021-20866: Advanced Custom Fields <= 5.10 Information Disclosure
CVE-2021-20866 - 5.4CVE-2024-37250: Advanced Custom Fields Pro Missing Authorization
CVE-2024-37250 - 5.4CVE-2024-37250: Advanced Custom Fields Pro Missing Authorization
CVE-2024-37250 - 5.1CVE-2024-9529: Advanced Custom Fields Limited Arbitrary Function Call
CVE-2024-9529
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C