code-projects Payroll Management System 1.0 update_account.php deduction sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.57 |
Summary
A vulnerability, which was classified as critical, has been found in code-projects Payroll Management System 1.0. Affected is an unknown function of the file update_account.php. Performing a manipulation of the argument deduction results in sql injection. This vulnerability is reported as CVE-2025-2985. The attack is possible to be carried out remotely. Moreover, an exploit is present. Other parameters might be affected as well.
Details
A vulnerability was found in code-projects Payroll Management System 1.0. It has been classified as critical. This affects an unknown functionality of the file update_account.php. The manipulation of the argument deduction with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-2985. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is shared for download at github.com. It is declared as proof-of-concept. Other parameters might be affected as well. By approaching the search of inurl:update_account.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
License
Website
- Vendor: https://code-projects.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 6.3
CNA 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: 🔍
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/30/2025 🔍03/30/2025 🔍
05/15/2025 🔍
Sources
Vendor: code-projects.orgAdvisory: github.com
Status: Not defined
CVE: CVE-2025-2985 (🔍)
GCVE (CVE): GCVE-0-2025-2985
GCVE (VulDB): GCVE-100-302037
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/30/2025 10:37Updated: 05/15/2025 04:58
Changes: 03/30/2025 10:37 (57), 03/31/2025 11:32 (30), 05/15/2025 04:58 (12)
Complete: 🔍
Submitter: NeoWSY
Cache ID: 216:737:103
Submit
Accepted
- Submit #523344: code-projects payroll-management-system-in-php v1.0 0/1 php sql injection (by NeoWSY)
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.