CVE-2026-9584: code-projects Project Management System Login chk.php sql injection
A security vulnerability has been detected in code-projects Project Management System 1.0. Affected is an unknown function of the file chk.php of the component Login. The manipulation leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used.
CVE-2026-9584 is a remotely reachable SQL injection in the login component of code-projects Project Management System 1.0. The published record says a public exploit exists, but the provided sources do not show confirmed active exploitation or a vendor patch.
Executive priority
Treat this as a high-priority exposure review if the product is deployed. Public exploit availability raises urgency, but remediation should be guided by confirmed product presence and vendor or project guidance.
Technical view
The issue affects chk.php in the Login component of code-projects Project Management System 1.0. It is classified as CWE-89 SQL injection and CWE-74 injection, with CVSS v2 7.5. The CVSS vector indicates network access, low complexity, no authentication, and partial confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to organizations running code-projects Project Management System 1.0, especially if the login page is internet-accessible. The source bundle does not identify other affected versions or forks.
Exploitation context
VulDB and the CVE description state that an exploit has been publicly disclosed and may be used. The provided bundle marks KEV as false, so there is no source-backed evidence here of confirmed active exploitation.
Researcher notes
Evidence is thin: the affected function is not named, and the bundle does not include a vendor patch statement. Avoid broad version assumptions. Validate by product/version fingerprinting and defensive review of the login data path.
Mitigation direction
Identify and inventory any Project Management System 1.0 deployments.
Restrict external access to the login route where feasible.
Check code-projects and advisory sources for vendor guidance or updates.
Monitor login and database logs for suspicious errors or unusual requests.
If internally maintained, review chk.php for parameterized query remediation.
Validation and detection
Confirm whether code-projects Project Management System 1.0 is deployed.
Check whether chk.php is reachable from untrusted networks.
Review web logs around the login endpoint for anomalous activity.
Verify whether any vendor or project update has been applied.
Confirm compensating access controls protect the login surface.
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.