Admin Side Data Storage for Contact Form 7 Plugin up to 1.1.1 on WordPress Read Status Update authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Admin Side Data Storage for Contact Form 7 Plugin up to 1.1.1 on WordPress. Impacted is an unknown function of the component Read Status Update Handler. Performing a manipulation results in authorization. This vulnerability is cataloged as CVE-2024-1779. There is no exploit available.
Details
A vulnerability was found in Admin Side Data Storage for Contact Form 7 Plugin up to 1.1.1 on WordPress (WordPress Plugin). It has been classified as problematic. This affects some unknown processing of the component Read Status Update Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity.
The weakness was shared 02/23/2024. The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2024-1779 since 02/22/2024. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.3
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: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
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
02/22/2024 🔍02/23/2024 🔍
02/23/2024 🔍
04/12/2026 🔍
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2024-1779 (🔍)
GCVE (CVE): GCVE-0-2024-1779
GCVE (VulDB): GCVE-100-254589
Entry
Created: 02/23/2024 07:42Updated: 04/12/2026 09:06
Changes: 02/23/2024 07:42 (37), 03/13/2024 15:40 (1), 03/13/2024 15:45 (12), 04/12/2026 09:06 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.