ZoomIt ZoomSounds Plugin up to 6.91 on WordPress deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in ZoomIt ZoomSounds Plugin up to 6.91 on WordPress. The impacted element is an unknown function. This manipulation causes deserialization. This vulnerability is handled as CVE-2025-47568. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical was found in ZoomIt ZoomSounds Plugin up to 6.91 on WordPress. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Deserialization of Untrusted Data vulnerability in ZoomIt ZoomSounds allows Object Injection. This issue affects ZoomSounds: from n/a through 6.91.
The weakness was released by Bonds. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2025-47568 since 05/07/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/08/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 the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 6.0
- 6.1
- 6.2
- 6.3
- 6.4
- 6.5
- 6.6
- 6.7
- 6.8
- 6.9
- 6.10
- 6.11
- 6.12
- 6.13
- 6.14
- 6.15
- 6.16
- 6.17
- 6.18
- 6.19
- 6.20
- 6.21
- 6.22
- 6.23
- 6.24
- 6.25
- 6.26
- 6.27
- 6.28
- 6.29
- 6.30
- 6.31
- 6.32
- 6.33
- 6.34
- 6.35
- 6.36
- 6.37
- 6.38
- 6.39
- 6.40
- 6.41
- 6.42
- 6.43
- 6.44
- 6.45
- 6.46
- 6.47
- 6.48
- 6.49
- 6.50
- 6.51
- 6.52
- 6.53
- 6.54
- 6.55
- 6.56
- 6.57
- 6.58
- 6.59
- 6.60
- 6.61
- 6.62
- 6.63
- 6.64
- 6.65
- 6.66
- 6.67
- 6.68
- 6.69
- 6.70
- 6.71
- 6.72
- 6.73
- 6.74
- 6.75
- 6.76
- 6.77
- 6.78
- 6.79
- 6.80
- 6.81
- 6.82
- 6.83
- 6.84
- 6.85
- 6.86
- 6.87
- 6.88
- 6.89
- 6.90
- 6.91
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
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
05/07/2025 🔍05/23/2025 🔍
05/23/2025 🔍
07/08/2025 🔍
Sources
Advisory: patchstack.comResearcher: Bonds
Status: Not defined
CVE: CVE-2025-47568 (🔍)
GCVE (CVE): GCVE-0-2025-47568
GCVE (VulDB): GCVE-100-310141
Entry
Created: 05/23/2025 15:37Updated: 07/08/2025 15:50
Changes: 05/23/2025 15:37 (63), 07/08/2025 15:50 (1)
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.