plainware Locatoraid Store Locator Plugin up to 3.9.50 on WordPress deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in plainware Locatoraid Store Locator Plugin up to 3.9.50 on WordPress. Affected by this vulnerability is an unknown functionality. The manipulation results in deserialization. This vulnerability is identified as CVE-2024-56283. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability classified as problematic has been found in plainware Locatoraid Store Locator Plugin up to 3.9.50 on WordPress. Affected is an unknown functionality. The manipulation with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Deserialization of Untrusted Data vulnerability in plainware.com Locatoraid Store Locator allows Object Injection.This issue affects Locatoraid Store Locator: from n/a through 3.9.50.
The weakness was released by Lvt-tholv2k. The advisory is available at patchstack.com. This vulnerability is traded as CVE-2024-56283 since 12/18/2024. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 01/07/2025).
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 best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 3.9.0
- 3.9.1
- 3.9.2
- 3.9.3
- 3.9.4
- 3.9.5
- 3.9.6
- 3.9.7
- 3.9.8
- 3.9.9
- 3.9.10
- 3.9.11
- 3.9.12
- 3.9.13
- 3.9.14
- 3.9.15
- 3.9.16
- 3.9.17
- 3.9.18
- 3.9.19
- 3.9.20
- 3.9.21
- 3.9.22
- 3.9.23
- 3.9.24
- 3.9.25
- 3.9.26
- 3.9.27
- 3.9.28
- 3.9.29
- 3.9.30
- 3.9.31
- 3.9.32
- 3.9.33
- 3.9.34
- 3.9.35
- 3.9.36
- 3.9.37
- 3.9.38
- 3.9.39
- 3.9.40
- 3.9.41
- 3.9.42
- 3.9.43
- 3.9.44
- 3.9.45
- 3.9.46
- 3.9.47
- 3.9.48
- 3.9.49
- 3.9.50
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (Patchstack): 🔍
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: DeserializationCWE: CWE-502 / CWE-20
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/18/2024 🔍01/07/2025 🔍
01/07/2025 🔍
01/07/2025 🔍
Sources
Advisory: patchstack.comResearcher: Lvt-tholv2k
Status: Not defined
CVE: CVE-2024-56283 (🔍)
GCVE (CVE): GCVE-0-2024-56283
GCVE (VulDB): GCVE-100-290466
Entry
Created: 01/07/2025 14:25Changes: 01/07/2025 14:25 (63)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.