CVE-2008-0850
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 · uneditedMultiple SQL injection vulnerabilities in Dokeos 1.8.4 allow remote attackers to execute arbitrary SQL commands via the (1) id parameter to whoisonline.php, (2) tracking_list_coaches_column parameter to main/mySpace/index.php, (3) tutor_name parameter to main/create_course/add_course.php, the (4) Referer HTTP header to index.php, and the (5) X-Fowarded-For HTTP header to main/admin/class_list.php.
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 confidenceMultiple SQL injection vulnerabilities in Dokeos 1.8.4 allow remote attackers to execute arbitrary SQL commands through unsanitized user input in five locations: the id parameter in whoisonline.php, tracking_list_coaches_column in main/mySpace/index.php, tutor_name in main/create_course/add_course.php, the Referer HTTP header in index.php, and the X-Forwarded-For HTTP header in main/admin/class_list.php.
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.8.4CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Identify Dokeos installation versionLook for a version file in the Dokeos installation directory (commonly version.php, changelog.txt, or in the admin interface under System Info or About). Alternatively, check the HTTP response headers or meta tags in the main index.php for version information.Affected if The detected version is Dokeos 1.8.4 exactly.
-
Confirm whoisonline.php is accessibleLocate whoisonline.php in the web root or document root directory of the Dokeos installation and verify the file exists.Affected if The file exists and the Dokeos version is 1.8.4.
-
Confirm main/mySpace/index.php is accessibleLocate the main/mySpace/ directory in the Dokeos installation and verify index.php exists.Affected if The file exists and the Dokeos version is 1.8.4.
-
Confirm main/create_course/add_course.php is accessibleLocate the main/create_course/ directory in the Dokeos installation and verify add_course.php exists.Affected if The file exists and the Dokeos version is 1.8.4.
-
Confirm main/admin/class_list.php is accessibleLocate the main/admin/ directory in the Dokeos installation and verify class_list.php exists.Affected if The file exists and the Dokeos version is 1.8.4.
A Dokeos 1.8.4 installation with these PHP files present is affected by CVE-2008-0850, as the SQL injection flaws exist in all five identified locations.
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 dataUpgrade to a patched version of Dokeos or implement parameterized queries/input validation for all identified parameters, including HTTP headers, to prevent SQL injection attacks.
- Consultation3.0 h
- Implementation12.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 $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0850 — 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-2008-0850 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