MoodleCMS
CVE-2014-0213
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities in mod/assign/locallib.php in the Assignment subsystem in Moodle through 2.3.11, 2.4.x before 2.4.10, 2.5.x before 2.5.6, and 2.6.x before 2.6.3 allow remote attackers to hijack the authentication of teachers for quick-grading requests.
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 Assignment module (mod/assign/locallib.php) contains multiple CSRF vulnerabilities in the quick-grading feature. The affected versions lack proper anti-CSRF token validation on grading submission forms, allowing attackers to craft malicious requests that trick authenticated teacher sessions into performing unintended grading actions.
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.11= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.1.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/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.
-
Determine Moodle installed versionCheck the version.php file in your Moodle root directory (version.php contains a $release or $version variable), or access Site Administration > Server > Environment to view the installed Moodle version.Affected if The installed version is <= 2.3.11, or matches 2.0.0 through 2.0.9, or is 2.1.0
-
Verify Assignment module is installedCheck for the presence of the mod/assign directory in your Moodle installation. Look for mod/assign/locallib.php file.Affected if The mod/assign directory and locallib.php file exist in the Moodle installation
-
Check if quick-grading feature is accessibleLog in as a teacher, navigate to a course with an assignment, and attempt to access the grading interface. The quick-grading panel appears on the submission grading page.Affected if Teachers can access the Assignment grading interface, which includes the quick-grading functionality
-
Inspect the vulnerable code for missing CSRF checksExamine mod/assign/locallib.php around the quick-grading submission handler. Look for missing sesskey() or confirm_sesskey() validation before processing grade updates.Affected if The code lacks sesskey() or confirm_session_key() calls in the quick-grading submission handler functions
You are affected if your Moodle version is <= 2.3.11 or between 2.0.0-2.0.9 or 2.1.0, and the Assignment module (mod/assign) with quick-grading is accessible to users.
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.10, 2.5.6, or 2.6.3 or later. Alternatively, apply the vendor patch to add CSRF token validation to all quick-grading form submissions in mod/assign/locallib.php.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0213 — 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-2014-0213 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