Xampp up to 8.1.4 on Windows Installation default permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Xampp up to 8.1.4 on Windows. It has been classified as critical. Affected by this issue is some unknown functionality of the component Installation. The manipulation leads to default permission. This vulnerability is uniquely identified as CVE-2022-29376. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Xampp up to 8.1.4 on Windows and classified as critical. This issue affects an unknown code block of the component Installation. The manipulation with an unknown input leads to a default permission vulnerability. Using CWE to declare the problem leads to CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 05/24/2022. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-29376 since 04/16/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Default permissionCWE: CWE-276 / CWE-266
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
04/16/2022 🔍05/24/2022 🔍
05/24/2022 🔍
08/15/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2022-29376 (🔍)
GCVE (CVE): GCVE-0-2022-29376
GCVE (VulDB): GCVE-100-200597
Entry
Created: 05/24/2022 07:19Updated: 08/15/2025 17:59
Changes: 05/24/2022 07:19 (37), 05/29/2022 11:01 (1), 06/20/2023 09:44 (2), 08/15/2025 17:59 (33)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Why did You use the cpe "xampp:xampp" instead of the official "apachefriends:xampp" provided by NVD Nist ?
Best Regards,
TEAM CERT
Do you want to use VulDB in your project?
Use the official API to access entries easily!