MoodleCMS
CVE-2012-6106
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 · uneditedcalendar/managesubscriptions.php in the Manage Subscriptions implementation in Moodle 2.4.x before 2.4.1 omits a capability check, which allows remote authenticated users to remove course-level calendar subscriptions by leveraging the student role and sending an iCalendar object.
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 confidenceMoodle 2.4.x before 2.4.1 has a missing function-level access control vulnerability in calendar/managesubscriptions.php. The file omits a capability check when processing requests to remove course-level calendar subscriptions, allowing authenticated users with only the student role to delete subscriptions they should not have permission to modify. This is an IDOR/authorization bypass where the application trusts the user-provided subscription ID without verifying the user has the required capabilities.
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.4.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
- 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.
-
Check installed Moodle versionLocate and read the version.php file in your Moodle root directory. Look for the $version variable which indicates the installed version (e.g., 2012112900 for 2.4.0).Affected if The installed version is exactly 2.4.0 (version number 2012112900).
-
Verify calendar module is enabledLog into Moodle as an administrator and navigate to Site Administration > Plugins > Activity modules > Manage activities, or check the config table for calendar module status.Affected if The calendar activity module is installed and enabled.
-
Inspect the vulnerable file for missing capability checkExamine the file calendar/managesubscription.php in your Moodle installation. Search for the code block that handles subscription deletion requests (typically around handling a 'delete' action). Verify whether a capability check such as require_capability('calendar/manageentries', ...) is present before processing the deletion.Affected if The file exists and lacks the proper capability check before processing deletion requests for course-level calendar subscriptions.
-
Test for IDOR as a student user (if feasible)Create a test scenario with two users: User A (teacher/admin) creates a course-level calendar subscription, then log in as User B (student) and attempt to access calendar/managesubscription.php with a subscription ID belonging to User A's course to see if deletion succeeds without proper authorization.Affected if An authenticated student user can delete calendar subscriptions belonging to other courses or users they should not have access to modify.
You are affected if running Moodle 2.4.0 with the calendar module enabled and the calendar/managesubscription.php file lacks the required capability check before processing deletion requests.
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 2.4.1 or later which includes the proper capability check for the Manage Subscriptions functionality, preventing unauthorized users from removing calendar subscriptions.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6106 — 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-6106 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