CVE-2026-5665
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security vulnerability has been detected in code-projects Online FIR System 1.0. Affected by this vulnerability is an unknown functionality of the file /Login/checklogin.php of the component Login. The manipulation of the argument email/password leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the login functionality of code-projects Online FIR System 1.0 at /Login/checklogin.php allows remote attackers to inject malicious SQL queries through the email and password parameters due to unsanitized user input being directly concatenated into SQL statements.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Online FIR System 1.0 installationLocate the web application's root directory and verify the presence of the Online FIR System by checking for typical FIR system files or directory structure.Affected if The application directory contains the FIR system files, particularly the /Login/ directory.
-
Identify the vulnerable login scriptLocate the file /Login/checklogin.php in the web application root directory.Affected if The file checklogin.php exists in the /Login/ directory of the application.
-
Inspect login code for SQL injection vulnerabilityOpen /Login/checklogin.php and examine the database query code, specifically looking for SQL statements that directly concatenate the 'email' and/or 'password' parameters without using prepared statements or parameterization.Affected if The code shows SQL queries where $_POST['email'] or $_POST['password'] variables are directly concatenated into the query string (e.g., $query = "SELECT * FROM users WHERE email='" . $_POST['email'] . "'").
-
Check if login form submits to vulnerable endpointExamine the HTML login form (typically in /Login/ or root) to confirm it submits to checklogin.php with email and password parameters.Affected if The login form submits user credentials via POST to checklogin.php using parameter names 'email' and 'password'.
The user is affected if the Online FIR System 1.0 is installed and checklogin.php contains direct SQL concatenation of email/password POST parameters without prepared statements or input sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements in checklogin.php to properly sanitize user input before executing database queries. Input validation and least-privilege database accounts should also be implemented.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5665 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5665 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data