dbcve.org
DokeosApplication

CVE-2006-2286

MEDIUM · 6.8 CVSS v2.0 Published 2006-05-10
Fix available
A fix is available. Upgrade to after 1.6.3 or later.
See remediation →
77/100
Remediation priority · High
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
Multiple PHP remote file inclusion vulnerabilities in claro_init_global.inc.php in Dokeos 1.6.3 and earlier, and Dokeos community release 2.0.3, allow remote attackers to execute arbitrary PHP code via a URL in the (1) rootSys and (2) clarolineRepositorySys parameters, and possibly the (3) lang_path, (4) extAuthSource, (5) thisAuthSource, (6) main_configuration_file_path, (7) phpDigIncCn, and (8) drs parameters to (a) testheaderpage.php and (b) resourcelinker.inc.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 confidence

Remote File Inclusion (RFI) vulnerability in Dokeos learning management system where claro_init_global.inc.php improperly handles multiple parameters (rootSys, clarolineRepositorySys, lang_path, and others) allowing attackers to inject arbitrary PHP code via remote URLs. The vulnerability exists in testheaderpage.php and resourcelinker.inc.php which include the vulnerable file.

MitigationUpgrade to a patched Dokeos version; as interim measures, disable allow_url_fopen/allow_url_include in php.ini, deploy a WAF, and implement strict input validation on all affected parameters to prevent URL injection.

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
DokeosApplication
Affected:<= 1.6.3
Dokeos Community ReleaseApplication
Affected:= 2.0.3

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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 checks

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

  1. Locate Dokeos installation and identify version
    Search for Dokeos installation directories (commonly /dokeos, /claroline, or in web root). Check for version.php or config files that contain the version number. Compare the installed version against affected ranges: <= 1.6.3 or = 2.0.3
    Affected if Installed version is Dokeos <= 1.6.3 or Dokeos Community Release = 2.0.3
  2. Verify vulnerable files exist
    Locate claro_init_global.inc.php in the Dokeos installation (typically in main/inc/ or similar). Also check for testheaderpage.php and resourcelinker.inc.php in the installation. These files must exist for the vulnerability to be exploitable
    Affected if The files claro_init_global.inc.php, testheaderpage.php, or resourcelinker.inc.php exist in the Dokeos installation
  3. Inspect claro_init_global.inc.php for vulnerable include patterns
    Open claro_init_global.inc.php and search for include/require statements using variables like $rootSys, $clarolineRepositorySys, or $lang_path without proper validation. Look for patterns like include($rootSys.$some_path) or require($clarolineRepositorySys)
    Affected if The file contains include/require statements that directly use unsanitized user-controlled variables for path construction
  4. Check if entry points include the vulnerable file
    Examine testheaderpage.php and resourcelinker.inc.php to confirm they include claro_init_global.inc.php, which passes the vulnerable parameters to PHP include/require functions
    Affected if testheaderpage.php or resourcelinker.inc.php includes claro_init_global.inc.php using variables that can be controlled via HTTP requests
  5. Confirm parameter control via HTTP
    Test if the vulnerable parameters (rootSys, clarolineRepositorySys, lang_path) can be supplied via GET or POST requests to testheaderpage.php or resourcelinker.inc.php. Attempt a controlled test (with a safe local file) to verify parameter injection is possible
    Affected if The affected parameters can be controlled through HTTP requests and influence file inclusion behavior

You are affected if you run Dokeos version 1.6.3 or earlier (or exactly version 2.0.3), the vulnerable files exist, and the include statements use unsanitized variables that can be controlled via HTTP parameters.

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
Upgrade available Upgrade to a release after 1.6.3
Interim mitigation

Upgrade to a patched Dokeos version; as interim measures, disable allow_url_fopen/allow_url_include in php.ini, deploy a WAF, and implement strict input validation on all affected parameters to prevent URL injection.

Fix this in Dokeos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-2286 — 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-2006-2286 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