SourceCodester Employee Task Management System 1.0 /edit-task.php task_id authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in SourceCodester Employee Task Management System 1.0. The impacted element is an unknown function of the file /edit-task.php. This manipulation of the argument task_id causes authorization. This vulnerability is tracked as CVE-2024-2574. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability classified as critical was found in SourceCodester Employee Task Management System 1.0. Affected by this vulnerability is some unknown functionality of the file /edit-task.php. The manipulation of the argument task_id with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed by Joshua Lictan (Hua Tong). The advisory is shared at github.com. This vulnerability is known as CVE-2024-2574. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. By approaching the search of inurl:edit-task.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: 8.1VulDB Meta Temp Score: 7.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 7.3
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: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
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/17/2024 🔍03/17/2024 🔍
03/17/2024 🔍
02/20/2025 🔍
Sources
Vendor: sourcecodester.comAdvisory: github.com
Researcher: Joshua Lictan (Hua Tong)
Status: Not defined
CVE: CVE-2024-2574 (🔍)
GCVE (CVE): GCVE-0-2024-2574
GCVE (VulDB): GCVE-100-257077
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2024 09:31Updated: 02/20/2025 19:32
Changes: 03/17/2024 09:31 (54), 03/17/2024 09:32 (1), 03/17/2024 15:24 (2), 05/01/2024 14:48 (2), 05/01/2024 14:51 (18), 02/20/2025 19:32 (20)
Complete: 🔍
Submitter: nochizplz
Committer: nochizplz
Cache ID: 216::103
Submit
Accepted
- Submit #299775: SOURCECODESTER Employee Task Management System 1.0 IDOR (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.