MoodleCMS
CVE-2012-0798
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 self-enrolment functionality in Moodle 2.1.x before 2.1.4 and 2.2.x before 2.2.1 allows remote authenticated users to obtain the manager role by leveraging the teacher role.
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's self-enrolment functionality contains a privilege escalation vulnerability where authenticated users with the teacher role can obtain the manager role by manipulating the self-enrolment process. This is a vertical privilege escalation beyond the intended teacher permissions.
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.2.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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/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.
-
Check the installed Moodle versionLog into Moodle as an administrator, navigate to Site administration > Server > Environment, or check the version.php file in the Moodle root directory. Look for the version number in the format x.x.xAffected if The installed version is 2.1.0, 2.1.1, 2.1.2, 2.1.3, or 2.2.0
-
Verify self-enrolment is enabledNavigate to Site administration > Plugins > Enrolment plugins and check if Self enrolment (Manual) or Self enrolment is listed and enabledAffected if Self-enrolment plugin is enabled and active on the site
-
Confirm teacher role exists and has site accessNavigate to Site administration > Users > Permissions > Define roles and verify that a teacher role is defined with authenticated user permissionsAffected if Teacher role is defined and assigned to users on the system
-
Check if teacher role can use self-enrolmentNavigate to Site administration > Plugins > Enrolment > Self enrolment, then check the Roles with self-enrolment capability section to see if Teacher role is listed as allowedAffected if Teacher role is granted permission to self-enrol in courses
The environment is affected if running Moodle version 2.1.0 through 2.2.0 and the self-enrolment plugin is enabled with teacher role having self-enrolment capability, allowing teachers to potentially escalate to manager privileges.
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.4 or 2.2.1 or later to patch the vulnerable self-enrolment functionality.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0798 — 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-0798 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