MoodleCMS
CVE-2010-1615
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 SQL injection vulnerabilities in Moodle 1.8.x before 1.8.12 and 1.9.x before 1.9.8 allow remote attackers to execute arbitrary SQL commands via vectors related to (1) the add_to_log function in mod/wiki/view.php in the wiki module, or (2) "data validation in some forms elements" related to lib/form/selectgroups.php.
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 versions 1.8.x before 1.8.12 and 1.9.x before 1.9.8 contain two SQL injection vulnerabilities: one in the wiki module's view.php via the add_to_log function, and another in lib/form/selectgroups.php due to insufficient data validation in form elements. Both allow remote attackers to execute arbitrary SQL commands.
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
= 1.8.1= 1.8.2= 1.8.3= 1.8.4= 1.8.5= 1.8.6= 1.8.7= 1.8.8= 1.8.9= 1.8.10= 1.8.11= 1.9.1CVSS 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
- Partial
AV:N/AC:L/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.
-
Identify installed Moodle versionAccess the admin interface: log in as administrator and navigate to Site Administration > Server > Environment, or check the version.php file in the Moodle root directory (look for the $release or $version variable)Affected if The version is 1.8.x before 1.8.12, or 1.9.x before 1.9.8 (specifically 1.8.1-1.8.11 or 1.9.1-1.9.7)
-
Determine if the wiki module is enabledLog in as administrator, go to Site Administration > Modules > Manage activities, and check if 'Wiki' is listed as visible/enabledAffected if The wiki module is enabled and the Moodle version is vulnerable as identified in step 1
-
Verify wiki module is actively usedCheck if any course has the wiki activity module added by reviewing course contents or querying the mdl_modules table where name='wiki' and visible=1Affected if The wiki module is enabled and actively present in any course on the Moodle installation
You are affected if your Moodle version is 1.8.1 through 1.8.11 or 1.9.1 through 1.9.7 AND the wiki module is enabled, since both conditions (vulnerable version and exposed attack surface) must be present for exploitation.
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 1.8.12, 1.9.8, or later. If immediate patching is not possible, consider temporarily disabling the wiki module and implementing input validation on form submissions as a compensating control.
Fix this in Moodle
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1615 — 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-2010-1615 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