megaoptim Rapid Cache Plugin up to 1.2.3 on WordPress cache containing sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in megaoptim Rapid Cache Plugin up to 1.2.3 on WordPress. The affected element is an unknown function. Such manipulation leads to use of cache containing sensitive information. This vulnerability is referenced as CVE-2024-12314. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in megaoptim Rapid Cache Plugin up to 1.2.3 on WordPress and classified as critical. Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a use of cache containing sensitive information vulnerability. Using CWE to declare the problem leads to CWE-524. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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 the cache with custom HTTP headers that may be unsanitized which can lead to Cross-Site Scripting.
The weakness was published by Joshua Provoste. The advisory is shared for download at wordfence.com. This vulnerability is handled as CVE-2024-12314 since 12/06/2024. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 02/18/2025). The MITRE ATT&CK project declares the attack technique as T1592.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.2
CNA Vector (Wordfence): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use of cache containing sensitive informationCWE: CWE-524
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/06/2024 🔍02/18/2025 🔍
02/18/2025 🔍
02/18/2025 🔍
Sources
Advisory: wordfence.comResearcher: Joshua Provoste
Status: Not defined
CVE: CVE-2024-12314 (🔍)
GCVE (CVE): GCVE-0-2024-12314
GCVE (VulDB): GCVE-100-296060
Entry
Created: 02/18/2025 07:32Updated: 02/18/2025 14:04
Changes: 02/18/2025 07:32 (63), 02/18/2025 14:04 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.