MoodleCMS
CVE-2012-6102
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 · uneditedlib.php in the Submission comments plugin in the Assignment module in Moodle 2.3.x before 2.3.4 and 2.4.x before 2.4.1 allows remote attackers to read or modify the submission comments (aka feedback comments) of arbitrary users via a crafted URI.
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 confidenceIDOR vulnerability in Moodle's Assignment module submission comments plugin (lib.php). The plugin fails to properly authorize access to submission comments, allowing remote attackers to read or modify feedback comments of arbitrary users via crafted URIs.
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.3.0= 2.3.1= 2.3.2= 2.3.3= 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/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.
-
Determine installed Moodle versionLog into Moodle as administrator and navigate to Site Administration > Server > Environment, or inspect the version.php file in the Moodle root directory. The version number is typically defined in a variable like $version or $release.Affected if The installed version matches 2.3.0, 2.3.1, 2.3.2, 2.3.3, or 2.4.0 exactly.
-
Verify Assignment module is enabledNavigate to Site Administration > Plugins > Activity modules > Manage activities, or check the course where assignments are being used. Confirm the Assignment activity module is installed and enabled.Affected if The Assignment module is present and enabled in the Moodle installation.
-
Confirm submission comments plugin is in useCheck if any courses are using the Assignment activity with the comments feature enabled. This can be verified by creating or viewing an assignment and checking if comments functionality is accessible to students or teachers.Affected if The Assignment submission comments feature is accessible to users, meaning the submission comments plugin is active.
-
Inspect vulnerable lib.php fileLocate the file mod/assignment/submission/comments/lib.php in the Moodle installation directory. Examine the function that handles viewing or editing comments for proper capability checks. The vulnerability exists if the code lacks capability checks before allowing access to submission comments.Affected if The lib.php file exists and lacks proper authorization checks in the comment access functions.
A user is affected if their Moodle installation version is exactly 2.3.0 through 2.3.3 or 2.4.0, the Assignment module is enabled, and the submission comments plugin is in use, allowing unauthorized access to comments.
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.3.4, 2.4.1, or later. Alternatively, apply the vendor patch to add proper authorization checks in the submission comments plugin.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6102 — 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-6102 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