MoodleCMS
CVE-2011-4283
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 · uneditedMoodle 1.9.x before 1.9.11 and 2.0.x before 2.0.2 places an IMS enterprise enrolment file in the course-files area, which allows remote attackers to obtain sensitive information via a request for imsenterprise-enrol.xml.
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 confidenceMoodle versions 1.9.x before 1.9.11 and 2.0.x before 2.0.2 incorrectly place an IMS Enterprise enrolment file (imsenterprise-enrol.xml) in the publicly accessible course-files directory. This allows unauthenticated remote attackers to directly request and download this file, potentially exposing sensitive enrolment data and system configuration information.
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.9.1= 1.9.2= 1.9.3= 1.9.4= 1.9.5= 1.9.6= 1.9.7= 1.9.8= 1.9.9= 1.9.10= 2.0.0= 2.0.1CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Determine installed Moodle versionAccess the Moodle admin interface and navigate to Site administration > Server > Environment, or check the version.php file in the Moodle root directory (search for $release or $version variables)Affected if The installed version is 1.9.x before 1.9.11, or 2.0.x before 2.0.2
-
Locate the imsenterprise-enrol.xml fileSearch for the file named imsenterprise-enrol.xml within the Moodle directory structure, particularly under the 'course-files' or 'moodledata' directory used for course content storageAffected if The file exists in the Moodle installation
-
Verify web accessibility of the fileUsing a web browser or curl command, attempt to access the file directly via HTTP (for example: http://your-moodle-site.com/imsenterprise-enrol.xml or http://your-moodle-site.com/course-files/imsenterprise-enrol.xml)Affected if The file can be downloaded or its contents displayed without authentication
You are affected if your Moodle version is 1.9.x before 1.9.11 or 2.0.x before 2.0.2 AND the imsenterprise-enrol.xml file exists in a web-accessible directory where unauthenticated users can request and download it.
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 Moodle 1.9.11+, 2.0.2+, or later. Alternatively, immediately remove the imsenterprise-enrol.xml file from the web-accessible course-files directory or configure web server access controls to deny public access.
Fix this in Moodle
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4283 — 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-2011-4283 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