dbcve.org
MoodleCMS

CVE-2006-4936

HIGH · 10.0 CVSS v2.0 Published 2006-09-23
Fix available
A fix is available. Upgrade to after 1.6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Moodle before 1.6.2 does not properly validate the module instance id when creating a course module object, which has unspecified impact and remote attack vectors.

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

Moodle before 1.6.2 fails to validate the module instance ID parameter when constructing course module objects, allowing attackers to manipulate object references through the parameter to access or manipulate data they should not have access to (IDOR vulnerability).

MitigationUpgrade to Moodle 1.6.2 or later which contains proper validation for module instance IDs. If immediate upgrade is not possible, implement input validation checks on all module instance parameters in course module creation routines.

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
MoodleCMS
Affected:<= 1.6.1= 1.6.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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Check the installed Moodle version
    Locate the version.php file in the Moodle root directory and read the $release or $version variable, or access the site administration page that displays the Moodle version
    Affected if The installed version is 1.6.0 or any version <= 1.6.1
  2. Identify course module creation code
    Examine the PHP files responsible for creating course module objects, specifically those that accept a module instance ID parameter from user input
    Affected if The code does not validate or verify the module instance ID parameter before using it to construct course module objects
  3. Verify module instance ID validation
    Search the course module creation routines for validation logic that checks whether the provided module instance ID belongs to the current user or course context
    Affected if No validation exists to ensure the module instance ID references an object the requesting user has permission to access or manipulate
  4. Test for IDOR via module instance parameter
    If you have access to course module creation functionality, attempt to submit a module instance ID that references a different course or module context than the one being created
    Affected if The system allows access to or manipulation of data belonging to a different course or module context without proper authorization checks

A Moodle installation is affected if it runs version 1.6.0 or any version <= 1.6.1 and the course module creation code lacks proper validation of the module instance ID parameter.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.6.1
Interim mitigation

Upgrade to Moodle 1.6.2 or later which contains proper validation for module instance IDs. If immediate upgrade is not possible, implement input validation checks on all module instance parameters in course module creation routines.

Recommended fix High confidence

1.6.2

  1. 1. Back up the existing Moodle database and all Moodle files
  2. 2. Download Moodle version 1.6.2 from the official Moodle repository (download.moodle.org)
  3. 3. Extract the Moodle 1.6.2 files to your server, overwriting the existing installation
  4. 4. Navigate to your Moodle site URL to trigger the automatic upgrade process
  5. 5. Follow any on-screen upgrade instructions to complete the migration
  6. 6. Verify the upgrade was successful by logging in and checking the Moodle version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Moodle Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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