MoodleCMS
CVE-2014-0125
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 · uneditedrepository/alfresco/lib.php in Moodle through 2.3.11, 2.4.x before 2.4.9, 2.5.x before 2.5.5, and 2.6.x before 2.6.2 places a session key in a URL, which allows remote attackers to bypass intended Alfresco Repository file restrictions by impersonating a file's owner.
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 confidenceThe Alfresco repository plugin in Moodle incorrectly places session keys in URLs, enabling attackers to bypass file access restrictions by impersonating file owners. This allows unauthorized access to files stored in the Alfresco Repository through session hijacking.
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
- None
AV:N/AC:M/Au:N/C:P/I:P/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.
-
Identify installed Moodle versionLocate the version.php file in your Moodle installation root directory and read the $release or $version variable, or run: grep -r '$version' | head -5 in the Moodle root to find version informationAffected if The installed version is <= 2.3.11, or matches any of these exact versions: 2.0.0 through 2.0.9, or 2.1.0
-
Check if Alfresco Repository plugin is installedLook for the Alfresco plugin directory in /repository/alfresco/ within your Moodle installation, or navigate to Site Administration > Plugins > Repositories > Manage repositories in the Moodle web interfaceAffected if The Alfresco Repository plugin is present in the /repository/ directory
-
Verify if Alfresco Repository plugin is enabledNavigate to Site Administration > Plugins > Repositories > Manage repositories in the Moodle web interface and check if Alfresco is listed as Enabled, or inspect the repository database table mdl_repository for enabled statusAffected if The Alfresco Repository plugin shows as Enabled or Available in the repository management interface
-
Inspect for URL-based session exposureCheck the Alfresco plugin source code in /repository/alfresco/locallib.php for functions that construct URLs containing session keys (look for 'sesskey' or 'session' in URL parameters), and review web server access logs for requests to Alfresco URLs containing session tokensAffected if The plugin code generates URLs with session keys as query parameters, or access logs show session tokens in Alfresco-related URL requests
You are affected if your Moodle version falls within the vulnerable range AND the Alfresco Repository plugin is installed and enabled, exposing session keys in URLs.
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 2.4.9, 2.5.5, 2.6.2, or later. Alternatively, disable the Alfresco Repository plugin if not required.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0125 — 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-0125 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