ACF Front End Editor: A security weakness
ACF Front End Editor is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- ACF Front End Editor
- Plugin slug
acf-front-end-editor- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Apr 30, 2024
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Apr 30, 2024 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update ACF Front End Editor to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The ACF Front End Editor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the update_texts() function in all versions up to, and including, 2.0.2. This makes it possible for authenticated attackers, with subscriber-level access and above, to update arbitrary post title, content, and ACF data.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N