CVE-2026-2173
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 vulnerability was identified in code-projects Online Examination System 1.0. Affected by this issue is some unknown functionality of the file login.php. The manipulation of the argument username/password leads to sql injection. The attack may be initiated remotely.
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 · moderate confidenceSQL injection vulnerability in the login.php file of Online Examination System 1.0 allows remote attackers to inject malicious SQL queries through the username and/or password parameters, potentially enabling authentication bypass, data exfiltration, or database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Examination System installationIdentify if the Fabian Online Examination System is deployed in your environment by locating the application files, typically in the web server's document root or application directory.Affected if The application is present on the server
-
Verify the installed versionLocate version information in the application, typically in a README file, about page, or within the source code comments. Check the login.php file header or any version configuration file.Affected if The installed version is exactly 1.0
-
Inspect login.php for SQL query handlingOpen the login.php file and examine how the username and password parameters are processed. Look for SQL queries that concatenate or embed user input directly into query strings without using prepared statements or parameter binding.Affected if Dynamic SQL queries concatenate user input from username or password fields
-
Check database connectivity configurationExamine the database configuration file (often db.php, config.php, or similar) to confirm the application uses a database that could be exploited via SQL injection.Affected if The application connects to a SQL database accessible via the login functionality
-
Test for SQL injection vulnerabilitySubmit SQL injection payloads in the username and/or password fields of the login form. Common test strings include single quotes, OR 1=1, or SQL comment sequences. Observe if the application returns database errors or behaves unexpectedly.Affected if The application returns SQL errors or bypasses authentication with injected SQL
You are affected if the Fabian Online Examination System version 1.0 is deployed and the login.php file contains dynamic SQL queries that incorporate username or password parameters without parameterized queries.
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 login.php for both username and password fields, implement input validation, and apply output encoding to prevent SQL injection attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2173 — 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-2173 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