dbcve.org
Online Reviewer SystemApplication · Fabian

CVE-2026-2223

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A security vulnerability has been detected in code-projects Online Reviewer System 1.0. Affected by this issue is some unknown functionality of the file /system/system/students/assessments/pretest/take/index.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack 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 · moderate confidence

SQL injection vulnerability in code-projects Online Reviewer System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /system/system/students/assessments/pretest/take/index.php. The unsanitized user input is directly used in database queries, enabling full database compromise.

MitigationImplement prepared statements/parameterized queries to properly sanitize the ID parameter before using it in SQL queries. If a vendor patch is available, apply it immediately. Consider implementing input validation as an additional defense layer.

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
Online Reviewer SystemApplication
Affected:= 1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm installed product and version
    Locate and examine any application files that contain version information, such as README files, version.php, or install scripts. Check the web root directory for identification files that specify the software name and version.
    Affected if The installed product is Fabian Online Reviewer System version 1.0 exactly.
  2. Identify the vulnerable file location
    Search the web server document root for the path /system/system/students/assessments/pretest/take/index.php. This file should exist in the web-accessible directory structure.
    Affected if The file /system/system/students/assessments/pretest/take/index.php exists on the server.
  3. Verify application is accessible over network
    Attempt to access the application URL endpoint that contains the vulnerable parameter path. Check if the web server responds to requests for the assessments module.
    Affected if The application is reachable over HTTP/HTTPS and the assessment functionality is accessible.
  4. Inspect the vulnerable code for unsanitized input
    Examine the source code of index.php in the /system/system/students/assessments/pretest/take/ directory. Look for SQL queries that directly use the ID parameter without prepared statements, parameter binding, or input sanitization.
    Affected if The code contains SQL queries that incorporate the ID parameter directly without parameterized queries or input validation.
  5. Test the ID parameter for SQL injection
    Send a crafted request to the endpoint with the ID parameter containing SQL injection payloads (e.g., ID=1' OR '1'='1). Observe if the application returns database errors or exhibits unexpected behavior indicating SQL injection is possible.
    Affected if The application returns SQL error messages or displays different content based on injection payloads, indicating unsanitized input is being processed.

A system is affected if it runs Fabian Online Reviewer System version 1.0 and the vulnerable PHP file at /system/system/students/assessments/pretest/take/index.php is accessible with unsanitized ID parameter handling in the code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries to properly sanitize the ID parameter before using it in SQL queries. If a vendor patch is available, apply it immediately. Consider implementing input validation as an additional defense layer.

Fix this in Online Reviewer System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2223 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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