MoodleCMS
CVE-2006-4935
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 · uneditedThe Database module in Moodle before 1.6.2 does not properly handle uploaded files, 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 confidenceThe Database module in Moodle versions before 1.6.2 contains a file upload vulnerability where uploaded files are not properly handled, allowing remote attackers to upload files to the server with potentially malicious content.
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
<= 1.6.1= 1.6.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Moodle versionAccess the Moodle administration page or check the version.php file in the Moodle root directory. Common paths include /lib/version.php or look for 'version' in the admin interface under Site administration > Server > PHP info or similar.Affected if The installed version is 1.6.0 or 1.6.1, or any version lower than 1.6.2.
-
Verify Database module is enabledLog in as administrator and navigate to Site administration > Modules > Manage activities, or check the mod/ directory for the database folder. The vulnerability exists in the Database activity module.Affected if The Database module (mod/database) is installed and enabled on the site.
-
Confirm file upload is permitted in Database modulesAccess any course where a Database activity exists, then go to the Database activity settings. Look for fields that allow file attachments or image uploads (often under field types like 'file' or 'image'). Check if the 'Allow file uploads' or similar option is enabled.Affected if File upload capability is enabled for any Database activity instance on the site.
A site is affected if it runs any Moodle version 1.6.0 or 1.6.1 (or earlier) AND has the Database module enabled with file upload functionality permitted.
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.
dbcve · scopedUpgrade Moodle to version 1.6.2 or later to patch the improper file handling in the Database module. If immediate upgrading is not possible, disable or restrict the Database module's file upload functionality as a temporary measure.
Moodle 1.6.2
- 1. Back up your existing Moodle installation directory and database before proceeding
- 2. Download Moodle 1.6.2 from the official Moodle downloads page (download.moodle.org)
- 3. Extract the Moodle 1.6.2 archive to a temporary location
- 4. Copy the new Moodle 1.6.2 files over your existing installation, replacing all files
- 5. Navigate to your Moodle site URL to trigger the upgrade process
- 6. Follow the on-screen upgrade prompts to complete the database migration
- 7. Verify the Database module is functioning correctly by testing file upload functionality
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
- 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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4935 — 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-2006-4935 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