CVE-2024-12314
Megaoptim Rapid Cache ≤ 1.2.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-12314 is a high-severity Use of Cache Containing Sensitive Information (CWE-524) vulnerability in Megaoptim Rapid Cache. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-12314 is a cache poisoning vulnerability affecting the Rapid Cache plugin for WordPress in all versions up to and including 1.2.3. The issue stems from the plugin storing HTTP headers in cached data without proper sanitization, enabling attackers to inject custom headers into the cache. Published on 2025-02-18, this flaw carries a CVSS v3.1 base score of 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) and is linked to CWE-524 and NVD-CWE-Other.
Unauthenticated attackers can exploit this vulnerability remotely with low complexity and no user interaction required. By sending crafted HTTP requests containing malicious headers, they can poison the site's cache, causing subsequent visitors to receive responses with unsanitized headers that facilitate cross-site scripting (XSS) attacks. The changed scope (S:C) in the CVSS vector indicates potential impact across security boundaries, with low confidentiality and integrity effects but no availability disruption.
Advisories from Wordfence and the plugin's WordPress.org page provide further details on this vulnerability. Security practitioners should consult these resources—https://www.wordfence.com/threat-intel/vulnerabilities/id/72b777ac-1870-4588-82fe-da96a784ec81?source=cve and https://wordpress.org/plugins/rapid-cache/—for patch information and recommended mitigation steps.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4840
Vulnerability Data
The Rapid Cache plugin for WordPress is vulnerable to Cache Poisoning in all versions up to, and including, 1.2.3. This is due to plugin storing HTTP headers in the cached data. This makes it possible for unauthenticated attackers to poison…
more
the cache with custom HTTP headers that may be unsanitized which can lead to Cross-Site Scripting.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V14.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces access authorizations so that cached sensitive data cannot be read by actors outside the intended sphere.
Directly prevents unauthorized transfer of information through shared resources such as caches.
Controls information flows to keep sensitive data from leaving its authorized control sphere via caches.
Requires cryptographic or other protection of sensitive information at rest, which covers cached data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege access permissions directly limits who can read cached sensitive data.
Protecting confidentiality of data-at-rest covers caches that persist sensitive information.
Protecting data-in-use can mitigate exposure when caches hold transient sensitive values.
Logical access controls on environments reduce the chance an outsider can reach the cache.
Hardened configuration baselines can disable or secure caching of sensitive data.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Information deletion ensures sensitive data is removed from caches when no longer needed.
Data leakage prevention can block unauthorized access to cached sensitive information.
A.8.26 only requires that security requirements (including those that could address caching of sensitive data) be identified and specified during development or acquisition; it does not itself mandate, design, or implement any change that would make the cache flaw stop being present in the resulting application.
A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, hardening, and data sanitization) during architecture and development; it does not itself remove an already-written cache that stores sensitive information outside the intended control sphere.
Secure coding practices prevent caching of sensitive data outside intended boundaries.