MoodleCMS
CVE-2012-0793
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 · uneditedMoodle 1.9.x before 1.9.16, 2.0.x before 2.0.7, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 allows remote attackers to view the profile images of arbitrary user accounts via unspecified vectors.
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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in Moodle's profile image handling. Attackers can view profile images of arbitrary user accounts without proper authorization, exposing sensitive user information. The vulnerability stems from insufficient access control checks when accessing user profile image resources.
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.9.1= 1.9.2= 1.9.3= 1.9.4= 1.9.5= 1.9.6= 1.9.7= 1.9.8= 1.9.9= 1.9.10= 1.9.11= 1.9.12CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 installed Moodle versionLocate the version.php file in your Moodle installation root directory (usually at /version.php or /lib/version.php) and read the $release or $version variable. Alternatively, access your Moodle site admin panel and check the Server > Environment page or the Notifications page which often displays the version.Affected if The installed version is 1.9.1, 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.9.9, 1.9.10, 1.9.11, or 1.9.12.
-
Verify profile picture functionality is accessibleCheck if user profile pictures are enabled in Moodle by navigating to Site Administration > Users > Permissions > User policies and verify the 'Default display of user pictures' setting is configured, or check if any user accounts have uploaded profile pictures.Affected if Profile pictures are enabled and users have uploaded profile images to their accounts.
-
Confirm user profile functionality is activeCheck if the Moodle user profile system is active by examining the database table 'user' for records where picture field is non-zero, or by attempting to access the profile page of any user account on the system.Affected if User profile pages exist and the profile picture field is populated for any user in the system.
Your environment is affected if you are running any Moodle version from 1.9.1 through 1.9.12 and your site has user profile pictures enabled with at least one user having uploaded a profile image.
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.9.16, 2.0.7, 2.1.4, or 2.2.1 or later to implement proper authorization checks for profile image access.
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-0793 — 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-0793 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