Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid user credentials
-
DeliveryAuthenticate to Employee Management System
-
ExploitNavigate to approve.php endpoint
-
ExecutionInject SQL syntax in id parameter
-
PersistExecute unauthorized database query
-
ImpactExfiltrate or modify employee data
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 valid user authentication (PR:L rating in CVSS vector) to access the Employee Management System and reach the approve.php endpoint. The vulnerability is triggered when user-supplied id and token parameters are submitted to the approve.php file without input sanitization. No special configuration or non-default settings are mentioned; any deployment of version 1.0 with the file accessible to authenticated users is vulnerable. Attack complexity is low (AC:L), meaning no special timing, race conditions, or brute-force activity is necessary - a single crafted request triggers the vulnerability. The scope is unchanged (S:U), meaning impact is confined to the affected system's database without crossing trust boundaries. |
| Impact | CVSS vector AV:N/AC:L/PR:L indicates this is a network-accessible vulnerability with low attack complexity requiring only low-level user privileges (authenticated access). EPSS data is unavailable, but the combination of authenticated requirement (PR:L) and public exploit availability suggests moderate real-world risk constrained by the authentication barrier. The E:P (Exploit maturity: Proof-of-Concept) flag confirms exploit code availability. Unlike unauthenticated SQLi vulnerabilities, this requires an attacker to first gain valid user credentials or session access, reducing the attack surface significantly. However, organizations deploying this system with weak password policies or shared credentials among staff face elevated risk. The low impact scores (C:L/I:L/A:L) indicate the vulnerability does not grant full database compromise or system-level access, but attackers can read sensitive employee data, modify records, or cause service disruption. |
| Exploit ScenarioDerived | An authenticated employee with low-level user access logs into the Employee Management System and discovers the vulnerable approve.php endpoint. The attacker crafts a malicious HTTP request injecting SQL syntax into the id parameter, such as id=1' OR '1'='1, allowing them to bypass approval logic and extract employee records from the database or modify approval statuses without authorization. Public exploit code from the referenced GitHub repository (zzzxc643/CVE1) details the exact injection payload syntax required. |
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 and token parameters in 370project/approve.php, enabling unauthorized database queries with low confidentiality, integrity, and availability impact. Publicly available exploit code exists and CVSS score of 6.3 reflects the attack's network accessibility despite requiring low-level authentication.
RemediationAI
Immediate remediation requires upgrading to a patched version of the Employee Management System if available from code-projects.org, or implementing a Web Application Firewall (WAF) rule to detect and block SQL injection patterns in the id and token parameters of approve.php requests. If no patched version exists, apply input validation by implementing strict whitelisting for the id parameter (numeric values only) and rejecting any token input containing SQL metacharacters. Use prepared statements with parameterized queries for all database interactions, replacing string concatenation SQL construction. Additionally, restrict access to approve.php to authenticated users over HTTPS, implement principle of least privilege for the database user account running queries, and enable database query logging to detect exploitation attempts. Monitor for unusual SQL error messages in application logs, which often indicate SQLi probing.
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 resides in a PHP application (370project/approve.php) that processes user-supplied input from the id and token HTTP parameters without proper sanitization or parameterized queries. SQL injection (CWE-89) occurs when an attacker concatenates malicious SQL syntax into these parameters, which are then executed directly against the backend database. The Employee Management System's PHP backend likely constructs dynamic SQL queries by string concatenation rather than using prepared statements with bound parameters, a common legacy development pattern in open-source project templates.
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 weakness has been identified in code-projects Employee Management System 1.0. Impacted is an unknown function of the file 370project/approve.php. Executing a manipulation of the argument id/token can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.
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-25831
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB