dbcve.org
ClarolineApplication

CVE-2006-7048

HIGH · 7.5 CVSS v2.0 Published 2007-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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 Claroline 1.7.5 allow remote attackers to execute arbitrary PHP code via a URL in the (1) clarolineRepositorySys parameter to (a) atutor.inc.php (b) db-generic.inc.php (c) docebo.inc.php (d) dokeos.1.6.inc.php (e) dokeos.inc.php (f) ganesha.inc.php (g) mambo.inc.php (h) moodle.inc.php (i) phpnuke.inc.php (j) postnuke.inc.php and (k) spip.inc.php in claroline/auth/extauth/drivers/; (2) includePath parameter in mambo.inc.php, postnuke.inc.php, and (l) inc/lib/event/init_event_manager.inc.php; and (3) rootSys parameter in (m) inc/lib/export_exe_tracking.class.php, a different set of vectors than CVE-2006-2284.

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 vulnerability in Claroline 1.7.5 allows attackers to execute arbitrary PHP code by supplying a URL to the clarolineRepositorySys, includePath, or rootSys parameters in multiple .inc.php files within claroline/auth/extauth/drivers/ and other lib directories. This is a classic RFI (Remote File Inclusion) where user-controlled input is used in include/require statements without sanitization, enabling remote code execution.

MitigationUpgrade to a patched version of Claroline beyond 1.7.5, or apply code fixes to validate/sanitize include path parameters and disable PHP's allow_url_fopen if possible. Immediately restrict access to the affected scripts if upgrading is not feasible.

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
ClarolineApplication
Affected:= 1.7.5

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

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

  1. Identify Claroline installation and version
    Locate the Claroline installation directory and check the version.php or similar version file. Common locations include the root directory or a 'claroline' subdirectory. Look for a version identifier in configuration or index files.
    Affected if The installed version is exactly 1.7.5 (Claroline Claroline)
  2. Locate vulnerable .inc.php files
    Search the web directory for .inc.php files within claroline/auth/extauth/drivers/ and lib directories. These files contain include/require statements using the clarolineRepositorySys, includePath, or rootSys parameters.
    Affected if These files exist and contain include/require statements using the vulnerable parameters without input validation
  3. Check PHP configuration for allow_url_fopen
    Create a PHP script with phpinfo() or check the php.ini configuration for the allow_url_fopen directive. This setting controls whether URL-aware fopen wrappers are enabled.
    Affected if allow_url_fopen is enabled (On), allowing remote URLs to be included
  4. Test for unauthenticated parameter access
    Examine the identified .inc.php files to determine if the vulnerable parameters (clarolineRepositorySys, includePath, rootSys) can be accessed without authentication. Check if these parameters are used directly in include/require statements.
    Affected if The parameters are accessible without authentication and are used in include/require without sanitization

A user is affected if they are running Claroline version 1.7.5 with the vulnerable .inc.php files present and accessible, and PHP's allow_url_fopen is enabled.

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

Upgrade to a patched version of Claroline beyond 1.7.5, or apply code fixes to validate/sanitize include path parameters and disable PHP's allow_url_fopen if possible. Immediately restrict access to the affected scripts if upgrading is not feasible.

Fix this in Claroline Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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