MoodleCMS
CVE-2011-4284
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 2.0.x before 2.0.2 allows remote attackers to obtain sensitive information from a myprofile (aka My profile) block by visiting a user-context page.
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 · moderate confidenceMoodle 2.0.x before 2.0.2 contains an information disclosure vulnerability in the myprofile (My profile) block. When a user visits a user-context page, the block exposes sensitive information that should not be visible to all users due to insufficient access control checks.
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.0.0= 2.0.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
- 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 versionLog into the Moodle site as administrator and navigate to Site Administration > Server > Environment, or check the version.php file in the Moodle root directory. The exact version number is displayed on the environment page or in the version variable.Affected if The installed version is exactly 2.0.0 or 2.0.1
-
Confirm myprofile block is installedNavigate to Site Administration > Plugins > Blocks > Manage blocks and verify that the 'My profile' block is listed as installed and available.Affected if The myprofile block is present in the installation
-
Test information disclosure from user-context pageCreate or use two different user accounts. As a non-admin user, navigate to a user profile page (user-context page) and observe whether the myprofile block displays sensitive information that should not be visible to this user, such as other users' private details or administrative data.Affected if The myprofile block displays sensitive information to unauthorized users when visiting user-context pages
-
Verify access control on myprofile blockReview the block's capability settings at Site Administration > Users > Permissions > Define roles, and check if the myprofile block allows viewing by any authenticated user regardless of whether they should have access to the profile being viewed.Affected if The block permissions allow unrestricted access to profile data
A site is affected if it runs Moodle 2.0.0 or 2.0.1 with the myprofile block enabled, and users can see sensitive information on user-context pages they should not have access to.
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.0.2 or later to resolve this vulnerability. If immediate upgrade is not feasible, apply the specific security patch for CVE-2011-4284 and verify the myprofile block no longer exposes unauthorized data.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4284 — 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-2011-4284 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