keerti1924 PHP-MYSQL-User-Login-System 1.0 /edit.php access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in keerti1924 PHP-MYSQL-User-Login-System 1.0. This vulnerability affects unknown code of the file /edit.php. This manipulation causes access control. The identification of this vulnerability is CVE-2024-1701. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability has been found in keerti1924 PHP-MYSQL-User-Login-System 1.0 (Database Software) and classified as critical. Affected by this vulnerability is some unknown functionality of the file /edit.php. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect integrity.
The weakness was shared 02/21/2024. The advisory is shared at github.com. This vulnerability is known as CVE-2024-1701. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way. By approaching the search of inurl:edit.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
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.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: Access controlCWE: CWE-284 / 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
02/21/2024 🔍02/21/2024 🔍
02/21/2024 🔍
02/13/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-1701 (🔍)
GCVE (CVE): GCVE-0-2024-1701
GCVE (VulDB): GCVE-100-254389
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/21/2024 11:34Updated: 02/13/2025 02:18
Changes: 02/21/2024 11:34 (42), 03/13/2024 08:11 (2), 03/13/2024 08:12 (18), 02/13/2025 02:18 (34)
Complete: 🔍
Submitter: omarexala
Cache ID: 216::103
Submit
Accepted
- Submit #278999: github.com/keerti1924 PHP-MYSQL-User-Login-System 1.0 Broken Access Control (by omarexala)
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.