CVE-2026-9450: code-projects Employee Management System psubmit.php sql injection
A security flaw has been discovered in code-projects Employee Management System 1.0. Affected is an unknown function of the file /psubmit.php. The manipulation of the argument pid results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks.
CVE-2026-9450 is an SQL injection in code-projects Employee Management System 1.0. A remote attacker with access to the application may manipulate the pid parameter in /psubmit.php, potentially affecting database confidentiality, integrity, and availability. Public exploit material exists, but the supplied sources do not show confirmed active exploitation.
Executive priority
Treat this as a moderate-priority remediation item. It affects a specific application version and appears to require authentication, but public exploit material raises urgency for any internet-facing or broadly accessible deployment.
Technical view
The CVE and VulDB records describe SQL injection in /psubmit.php through the pid argument. CVSS v2 is 6.5 with network access, low complexity, and single authentication required. The affected product is code-projects Employee Management System 1.0. The vulnerable function is not identified in the source bundle.
Likely exposure
Exposure is likely limited to organizations running code-projects Employee Management System 1.0, especially if the application or /psubmit.php is reachable by remote authenticated users. The bundle does not identify other versions or derived products as affected.
Exploitation context
The source bundle says exploit code has been publicly released and may be used for attacks. CISA KEV status is false, and no cited source in the bundle confirms active exploitation in the wild. Authentication appears required based on the CVSS vector and CTI tagging.
Researcher notes
Evidence is sparse: the vulnerable function is unknown, and the bundle does not include a vendor patch statement. Prioritize confirming product/version exposure, reachability, authentication requirements, and whether application code uses safe query handling around pid in /psubmit.php.
Mitigation direction
Check code-projects and CVE/VulDB guidance for any fixed release or official workaround.
Restrict external access to Employee Management System and /psubmit.php where business permits.
Ensure only trusted users can authenticate to the application.
Reduce database account privileges used by the application.
Monitor requests to /psubmit.php for abnormal pid values and access patterns.
Validation and detection
Inventory whether code-projects Employee Management System 1.0 is deployed.
Confirm whether /psubmit.php is reachable from untrusted networks or user groups.
Review web and application logs for suspicious /psubmit.php pid activity.
Verify authentication controls limit access to the affected workflow.
Confirm database privileges are minimal for the application account.
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.