Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain application credentials
-
DeliveryAuthenticate to application
-
ExploitCraft malicious SQL in ID parameter
-
ExecutionSubmit DELETE request to 370project/delete.php
-
PersistExecute unauthorized database query
-
ImpactExfiltrate or modify employee records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires authenticated access to the application (PR:L in CVSS indicates low privilege authentication level needed, such as standard employee account). The 370project/delete.php endpoint must be accessible and accept the ID parameter without server-side restrictions or Web Application Firewall blocking. The application must process the ID parameter in SQL queries without parameterized statements, input encoding, or validation. No special configuration or non-default deployment mode is indicated; standard installation of version 1.0 is vulnerable. Exploitation is NOT limited to administrators - any authenticated user can craft the malicious request. |
| Impact | CVSS 5.3 with network accessibility (AV:N) but authenticated requirement (PR:L) creates a moderate baseline risk. The CVSS 4.0 vector shows limited confidentiality, integrity, and availability impact (VC:L/VI:L/VA:L), suggesting database access rather than full system compromise. Exploitation probability marked as P suggests publicly known but not actively widespread. The presence of publicly available exploit code lowers attacker barrier significantly. Real-world risk depends critically on: (1) whether the application is internet-exposed or internal-only, (2) ease of obtaining authentication credentials, and (3) sensitivity of data stored in the Employee Management System. For organizations with strict internal access controls, risk is substantially lower than CVSS score suggests. For internet-facing deployments with weak authentication, risk is elevated. The limited scope of data access (not system-wide) reduces impact compared to higher-severity SQLi vulnerabilities. |
| Exploit ScenarioDerived | An authenticated user (employee or contractor with application access) exploits the delete.php ID parameter by injecting SQL commands, such as modifying the query from 'DELETE FROM employees WHERE id=5' to 'DELETE FROM employees WHERE id=5 OR 1=1', enabling unauthorized data deletion or manipulation. With publicly available exploit code hosted on GitHub, discovery and exploitation by internal or external attackers with credentials is straightforward. Exploitation requires valid authentication credentials but does not require user interaction or administrative privileges. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 27, 2026
SQL injection in code-projects Employee Management System 1.0 allows authenticated remote attackers to manipulate the ID argument in 370project/delete.php, leading to unauthorized database queries with limited confidentiality and integrity impact. Publicly available exploit code exists; CVSS 5.3 reflects moderate risk limited by authentication requirement and restricted data access scope.
RemediationAI
Immediate action: upgrade to a patched version released by code-projects (version number not confirmed in available advisories - contact vendor at code-projects.org for confirmed patch release). If upgrade is not immediately available, implement compensating controls: (1) restrict network access to 370project/delete.php via firewall or Web Application Firewall (WAF) rules to internal IP ranges only, reducing AV:N to effectively AV:L; (2) enforce strict input validation on the ID parameter using whitelist-based validation for expected numeric or alphanumeric formats; (3) implement parameterized SQL statements or prepared statement APIs in the PHP code to prevent SQL injection entirely; (4) apply principle of least privilege to the database user account used by the application, limiting it to DELETE operations only on necessary tables. Each control should be tested thoroughly before deployment to avoid blocking legitimate delete operations.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the delete.php file, a common application endpoint for record removal in web-based management systems. The ID parameter is passed directly into SQL queries without proper input sanitization or parameterized statement preparation, exemplifying CWE-89 (SQL Injection). PHP applications processing user-supplied input into SQL commands without encoding or prepared statements are particularly vulnerable. The CPE designation indicates all versions of the product before patching are affected, though version 1.0 is explicitly confirmed vulnerable.
Know when Employee Management System gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionCVE.org
A vulnerability was identified in code-projects Employee Management System 1.0. This vulnerability affects unknown code of the file 370project/delete.php. Such manipulation of the argument ID leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might be used.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Employee Management System
View allSQL Injection vulnerability in Sourcecodester Employee Management System v1.0 allows attackers to run arbitrary SQL comm
SQL Injection vulnerability in Employee Management System v1.0 allows attackers to run arbitrary SQL commands via the ad
Employee Managment System v1.0 was discovered to contain a SQL injection vulnerability via the mailud parameter at /apro
Employee Managment System v1.0 was discovered to contain a SQL injection vulnerability via the pwd parameter at /aproces
An issue in Employee Managment System v1.0 allows attackers to bypass authentication via injecting a crafted payload int
A vulnerability was found in SourceCodester Employee Management System 1.0. Rated critical severity (CVSS 9.8), this vul
A vulnerability was found in SourceCodester Employee Management System. Rated critical severity (CVSS 9.8), this vulnera
A vulnerability was found in SourceCodester Employee Management System. Rated critical severity (CVSS 9.8), this vulnera
A vulnerability has been found in SourceCodester Employee Management System and classified as critical. Rated critical s
A vulnerability classified as problematic was found in SourceCodester Employee Management System 1.0. Rated high severit
Employee Managment System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /edit.php
Employee Managment System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /delete.p
EUVD-2026-25821
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB