SourceCodester Computer Inventory System 1.0 add-computer.php model cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SourceCodester Computer Inventory System 1.0. It has been rated as problematic. Impacted is an unknown function of the file /endpoint/add-computer.php. Performing a manipulation of the argument model results in cross site scripting. This vulnerability is identified as CVE-2024-2066. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability was found in SourceCodester Computer Inventory System 1.0. It has been classified as problematic. This affects an unknown function of the file /endpoint/add-computer.php. The manipulation of the argument model with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity.
The weakness was released 03/01/2024 by Joshua Lictan (Hua Tong). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-2066. It demands that the victim is doing some kind of user interaction. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The exploit is shared for download at github.com. It is declared as proof-of-concept. By approaching the search of inurl:endpoint/add-computer.php it is possible to find vulnerable targets with Google Hacking.
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
Vendor
Name
Version
License
Website
- Vendor: https://www.sourcecodester.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.6
VulDB Base Score: 2.4
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CNA Base Score: 2.4
CNA Vector (VulDB): 🔍
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
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
03/01/2024 🔍03/01/2024 🔍
03/01/2024 🔍
04/18/2025 🔍
Sources
Vendor: sourcecodester.comAdvisory: github.com
Researcher: Joshua Lictan (Hua Tong)
Status: Not defined
CVE: CVE-2024-2066 (🔍)
GCVE (CVE): GCVE-0-2024-2066
GCVE (VulDB): GCVE-100-255381
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/01/2024 08:21Updated: 04/18/2025 06:51
Changes: 03/01/2024 08:21 (41), 03/01/2024 11:15 (2), 04/03/2024 18:34 (16), 04/03/2024 18:42 (18), 12/17/2024 21:42 (20), 04/18/2025 06:51 (3)
Complete: 🔍
Submitter: nochizplz
Committer: nochizplz
Cache ID: 216::103
Submit
Accepted
- Submit #289932: sourcecodester Computer Inventory System 1.0 Stored xss (by nochizplz)
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.