CVE-2026-9451: code-projects Employee Management System applyleaveprocess.php sql injection
A weakness has been identified in code-projects Employee Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /process/applyleaveprocess.php. This manipulation of the argument ID causes sql injection. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks.
This vulnerability affects code-projects Employee Management System 1.0. A remote authenticated user may manipulate the leave-application process to trigger SQL injection, risking database confidentiality, integrity, and availability. Public proof-of-concept material exists, but the provided sources do not show confirmed active exploitation.
Executive priority
Prioritize remediation if this system is internet-facing, handles employee data, or has broad user access. The issue is not marked KEV, but public exploit availability makes delay risky for exposed deployments.
Technical view
CVE-2026-9451 is SQL injection in /process/applyleaveprocess.php through the ID argument. VulDB rates it CVSS v2 6.5 with network access, low complexity, and authentication required. The CVE maps to CWE-89 and CWE-74. No vendor patch or mitigation is identified in the supplied sources.
Likely exposure
Exposure is likely limited to organizations running code-projects Employee Management System 1.0, especially where authenticated users can reach /process/applyleaveprocess.php. Public internet exposure increases urgency, but authentication is required according to the CVSS vector.
Exploitation context
The sources state that exploit material is publicly available and could be used for attacks. KEV is false, and no supplied source confirms active exploitation. Treat this as credible public PoC risk, not proven in-the-wild exploitation.
Researcher notes
Do not assume unauthenticated exploitation; the CVSS vector says authentication is required. The vulnerable parameter is identified as ID, but the affected function is otherwise unspecified. Sources provide no official patch, fixed version, or confirmed exploitation telemetry.
Mitigation direction
Check code-projects and VulDB for vendor patch or mitigation guidance.
Restrict access to the application to trusted networks or VPN users.
Review user accounts and remove unnecessary authenticated access.
If maintaining code, review ID handling for parameterized queries and validation.
Monitor database and application logs for suspicious leave-processing activity.
Validation and detection
Inventory systems for code-projects Employee Management System 1.0.
Confirm whether /process/applyleaveprocess.php exists and is reachable.
Verify whether the route requires authentication in deployed configuration.
Review logs for unusual ID parameter errors or database exceptions.
Check whether any vendor update or local fix has already been applied.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-74 · source CWE mapping
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.