MoodleCMS
CVE-2012-2366
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 · uneditedmod/data/preset.php in Moodle 2.1.x before 2.1.6 and 2.2.x before 2.2.3 does not properly iterate through an array, which allows remote authenticated users to overwrite arbitrary database activity presets via unspecified 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 vulnerability exists in Moodle's mod/data/preset.php where improper array iteration allows remote authenticated users to overwrite arbitrary database activity presets. The code fails to properly validate or scope array traversal when processing preset data, enabling preset manipulation beyond the intended boundaries.
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
= 2.1.0= 2.1.1= 2.1.2= 2.1.3= 2.1.4= 2.1.5= 2.2.0= 2.2.1= 2.2.2CVSS 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
- Single
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Moodle versionLog into the Moodle admin panel and navigate to Site administration > Server > Environment, or check the version.php file in the Moodle root directory (look for $release or $version variables)Affected if The installed version is 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.2.0, 2.2.1, or 2.2.2
-
Verify Data activity module is enabledGo to Site administration > Plugins > Activity modules > Manage activities, or query the mdl_modules table in the database for the 'data' module with status = 1Affected if The Data activity module is installed and enabled on the site
-
Confirm preset functionality is accessibleCheck if any course has a Data activity instance created, which would allow access to mod/data/preset.php through the web interface. Look in mdl_data table for active instances.Affected if There are active Data activity instances where users can access the preset import/export feature
-
Check for custom presets in the filesystemInspect the mod/data/preset directory within the Moodle installation for any custom preset folders that could be targeted for overwritingAffected if Custom presets exist in the mod/data/preset directory that could be manipulated through the vulnerability
You are affected if your Moodle version is 2.1.0-2.1.5 or 2.2.0-2.2.2 and the Data activity module is enabled with active instances that allow users to access preset functionality.
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 Moodle to version 2.1.6 or later for the 2.1.x branch, or 2.2.3 or later for the 2.2.x branch. This is a logic error in preset handling that was corrected in the patched releases.
Fix this in Moodle
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2366 — 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-2012-2366 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