Quick answers
- Is CVE-2026-112313 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112313 being exploited in the wild.
- How severe is CVE-2026-112313?
- High severity, with a CVSS score of 7.1, published 22 October 2026.
- Which products and versions are affected?
- ACF Extended through 0.9.2.7.
- Is there a fix for CVE-2026-112313?
- Yes: fixed in 0.9.2.8. Until then: Update the ACF Extended plugin to version 0.9.2.8 or later immediately. If unable to update immediately, Patchstack reports a mitigation rule is available to block attacks until the plugin can be patched. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112313 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112313?
- Check whether you run ACF Extended at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.9.2.8
Update the ACF Extended plugin to version 0.9.2.8 or later immediately. If unable to update immediately, Patchstack reports a mitigation rule is available to block attacks until the plugin can be patched.
Technical details
This is a stored XSS vulnerability in ACF Extended versions up to 0.9.2.7 resulting from improper neutralization of user-supplied input during web page generation. The vulnerability requires user interaction (a privileged user clicking a malicious link or visiting a crafted page), but once stored on the site, the malicious script executes for all visitors. The vulnerability is fixed in version 0.9.2.8 and later.
Affected products
- ACF Extended ACF Extended through 0.9.2.7
Timeline
- 2026-10-22: disclosed: Vulnerability published on NVD
- 2026-10-20: patched: Patched version 0.9.2.8 released
- 2026-08-19: other: Reported by Asim Alshaya