SourceCodester Lead Management System 1.0 removeLead.php ID sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in SourceCodester Lead Management System 1.0. Affected is an unknown function of the file removeLead.php. The manipulation of the argument ID leads to sql injection. This vulnerability is traded as CVE-2022-47861. There is no exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in SourceCodester Lead Management System 1.0. It has been rated as critical. This issue affects an unknown function of the file removeLead.php. The manipulation of the argument id
with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Lead Management System v1.0 is vulnerable to SQL Injection via the id parameter in removeLead.php.
The weakness was published 01/11/2023. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-47861 since 12/21/2022. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
By approaching the search of inurl:removeLead.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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
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
12/21/2022 🔍01/11/2023 🔍
01/11/2023 🔍
04/09/2025 🔍
Sources
Vendor: sourcecodester.comAdvisory: github.com
Status: Not defined
CVE: CVE-2022-47861 (🔍)
GCVE (CVE): GCVE-0-2022-47861
GCVE (VulDB): GCVE-100-218015
Entry
Created: 01/11/2023 06:52 PMUpdated: 04/09/2025 09:17 PM
Changes: 01/11/2023 06:52 PM (39), 02/04/2023 06:40 AM (11), 04/09/2025 09:17 PM (16)
Complete: 🔍
Cache ID: 18:2FA:40
No comments yet. Languages: en.
Please log in to comment.