CVE-2026-2195
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 has been found in code-projects Online Reviewer System 1.0. This vulnerability affects unknown code of the file /system/system/admins/assessments/pretest/questions-view.php. The manipulation of the argument ID leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed to the public 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 confidenceSQL 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/admins/assessments/pretest/questions-view.php. The critical CVSS 9.8 score indicates unauthenticated remote code execution potential through 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 the Online Reviewer System is installedSearch the web root directory for files or directories containing 'Fabian', 'Online Reviewer', or check for the presence of the 'system' directory structure commonly used by this applicationAffected if The application is present on the server
-
Identify the installed versionCheck version files, readme files, or examine the main entry point of the application for a version string. Compare against version 1.0Affected if The installed version is exactly 1.0 (Fabian Online Reviewer System)
-
Locate the vulnerable PHP fileVerify the existence of /system/system/admins/assessments/pretest/questions-view.php within the application web rootAffected if The file questions-view.php exists in the expected path
-
Verify the application is accessibleCheck if the web server is running and the application is reachable over HTTP/HTTPS. Attempt to access the vulnerable endpoint URL patternAffected if The application responds to HTTP requests on the network
-
Confirm parameter processing in the vulnerable fileReview the source code of questions-view.php and locate any SQL queries that incorporate the 'ID' parameter without prepared statements or parameter bindingAffected if The code uses the ID parameter directly in SQL queries without sanitization or parameterized queries
A user is affected if they have Fabian Online Reviewer System version 1.0 installed with the questions-view.php file accessible and the ID parameter is processed in SQL queries without proper 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 dataImplement prepared statements/parameterized queries for all database operations involving the ID parameter, add input validation and sanitization, deploy a WAF with SQL injection rules as a compensating control, and conduct a broader code audit for additional SQL injection vulnerabilities in the application.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2195 — 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-2195 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