dbcve.org
MoodleCMS

CVE-2012-6105

MEDIUM · 5.0 CVSS v2.0 Published 2013-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
blog/rsslib.php in Moodle 2.1.x before 2.1.10, 2.2.x before 2.2.7, 2.3.x before 2.3.4, and 2.4.x before 2.4.1 continues to provide a blog RSS feed after blogging is disabled, which allows remote attackers to obtain sensitive information by reading this feed.

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 confidence

In Moodle versions 2.1.x through 2.4.x before their respective security patches, the blog/rsslib.php script fails to properly check whether the blogging feature has been disabled in the system configuration. This allows the RSS feed endpoint to remain accessible and serve blog content even when an administrator has explicitly disabled the blogging functionality, resulting in unintended information disclosure of potentially sensitive blog entries to unauthorized users.

MitigationUpgrade Moodle to version 2.1.10, 2.2.7, 2.3.4, or 2.4.1 or later. Alternatively, if immediate patching is not feasible, consider restricting access to the /blog/rsslib.php endpoint via web server configuration (e.g., IP whitelisting or authentication requirements) until the upgrade can be performed.

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
Affected:= 2.1.0= 2.1.1= 2.1.2= 2.1.3= 2.1.4= 2.1.5= 2.1.6= 2.1.7= 2.1.8= 2.1.9= 2.2.0= 2.2.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Moodle version
    Locate the version.php file in your Moodle installation root directory (usually /lib/version.php or /version.php) and read the $release or $version variable. Alternatively, access Site Administration > Server > Environment to view the Moodle version.
    Affected if The installed version is 2.1.0 through 2.2.1 (as listed in affected products) or falls within the 2.1.x through 2.4.x range mentioned in the summary.
  2. Verify blogging feature status
    Access Site Administration > Features > Experimental features and check if 'Enable blog' is set to No/Disabled. Alternatively, inspect the mdl_config table in the database for the record where name = 'enableblog' and check if value = 0.
    Affected if The blogging feature is explicitly disabled (enableblog config set to 0 or the UI shows blogging as disabled).
  3. Test RSS feed endpoint accessibility
    Attempt to access the /blog/rsslib.php endpoint directly via HTTP request (e.g., http://yourmoodle/blog/rsslib.php). Observe whether the RSS feed returns blog content or an error message.
    Affected if The RSS feed endpoint returns blog entries or valid XML content even when the blogging feature is disabled in step 2, indicating the access control bypass is present.
  4. Check for security patch applied
    Examine the blog/rsslib.php file in your installation for the fix. Look for code that validates the blogging enable/disable status before serving RSS content. The patched version should contain a check similar to 'if (!empty($CFG->enableblog))' or 'if ($CFG->enableblog)' before processing.
    Affected if The blog/rsslib.php file does not contain a check to verify that blogging is enabled before serving content, or the check is missing/inadequate.

You are affected if your Moodle version is 2.1.0-2.2.1 (or any 2.1.x-2.4.x version) AND the RSS feed at /blog/rsslib.php remains accessible and serves content even when you have explicitly disabled the blogging feature in configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Moodle to version 2.1.10, 2.2.7, 2.3.4, or 2.4.1 or later. Alternatively, if immediate patching is not feasible, consider restricting access to the /blog/rsslib.php endpoint via web server configuration (e.g., IP whitelisting or authentication requirements) until the upgrade can be performed.

Fix this in Moodle Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-6105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-6105 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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