CVE-2026-2197
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 determined in code-projects Online Reviewer System 1.0. Impacted is an unknown function of the file /system/system/admins/assessments/pretest/exam-delete.php. This manipulation of the argument test_id causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceA critical SQL injection vulnerability exists in the code-projects Online Reviewer System 1.0 within the exam-delete.php file. The test_id parameter passed to this endpoint is not properly sanitized before being used in database queries, allowing remote attackers to inject malicious SQL statements and potentially exfiltrate, modify, or delete database contents.
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 Fabian Online Reviewer System installationLocate the web application directory and identify if the Fabian Online Reviewer System is deployed. Check for characteristic files such as index.php, login pages, or reviewer-specific modules.Affected if The Fabian Online Reviewer System version 1.0 is installed and accessible on the server.
-
Verify exam-delete.php existsSearch the web root directory for the file exam-delete.php. This is the vulnerable endpoint mentioned in the CVE.Affected if The file exam-delete.php exists in the application directory structure.
-
Check test_id parameter handling in exam-delete.phpOpen exam-delete.php and examine how the test_id parameter is processed. Look for direct insertion of the test_id parameter into SQL queries without using prepared statements or parameter binding.Affected if The test_id parameter is used directly in SQL queries without sanitization, prepared statements, or parameterized queries.
-
Verify application versionCheck the application's version information, typically found in a README file, version config, or the main index page footer.Affected if The installed version is exactly 1.0 of the Fabian Online Reviewer System.
-
Test the vulnerable endpointIf accessible, send a crafted request to exam-delete.php with a test_id value to observe database behavior. Use a safe test value and monitor for SQL error messages or unexpected query execution.Affected if The application executes the test_id parameter in SQL context without validation, allowing injection.
A user is affected if the Fabian Online Reviewer System version 1.0 is installed and the exam-delete.php file processes the test_id parameter in SQL queries 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 or prepared statements, implement proper input validation on the test_id parameter, and apply principle of least privilege to the database user account. Consider deploying a WAF as an additional layer of defense.
- 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-2197 — 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-2197 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