MoodleCMS
CVE-2025-67857
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 · uneditedA flaw was found in moodle. During anonymous assignment submissions, user identifiers were inadvertently exposed in URLs. This data exposure allows unauthorized viewers to see internal user IDs, compromising the intended anonymity and potentially leading to information disclosure.
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 confidenceIn Moodle's anonymous assignment submission feature, the application improperly includes user identifiers in URLs generated for submission pages. When students submit assignments anonymously, the system constructs URLs that contain internal user IDs (likely as parameters or in the path), allowing anyone with access to these URLs to correlate anonymous submissions with specific user accounts.
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
< 4.1.21>= 4.4.0, < 4.4.11>= 4.5.0, < 4.5.8>= 5.0.0, < 5.0.4= 5.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Determine installed Moodle versionAccess Site Administration > Server > Environment or check the version.php file in the Moodle root directory (look for $version variable)Affected if The installed version falls within any of the affected ranges: < 4.1.21; >= 4.4.0 and < 4.4.11; >= 4.5.0 and < 4.5.8; >= 5.0.0 and < 5.0.4; or exactly version 5.1.0
-
Identify active assignment activities with anonymous submissionGo to Site Administration > Plugins > Activity modules > Assignment, or navigate to a course and view assignments. Check each assignment settings for 'Anonymous submissions' option enabledAffected if Any assignment activity has anonymous submissions enabled and the Moodle version is affected
-
Inspect submission URLs for user identifiersSubmit a test assignment as a student with anonymous submission enabled, then view the generated submission URL. Examine the URL for parameters or path segments containing numeric user IDs (commonly 'userid', 'id', 'sid' with numeric values)Affected if The generated submission URL contains visible user identifiers such as user ID numbers that could correlate anonymous submissions to users
-
Verify assignment grading configurationAccess Site Administration > Plugins > Activity modules > Assignment > Default settings, or check individual assignment settings under 'Grading' sectionAffected if Anonymous grading is not enforced at the site level, allowing instructors to accidentally disable it per-assignment
You are affected if your Moodle version is within the affected ranges AND you have assignment activities using anonymous submissions enabled, with URLs containing user identifiers.
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.
dbcve · scoped4.1.214.4.114.5.8
The fix requires modifying the assignment submission URL generation logic to strip or omit user identifiers when anonymous mode is enabled. Administrators should verify that all assignment activities have anonymous grading properly configured and enforced at the application level.
Upgrade to minimum fixed version: 4.1.21, 4.4.11, 4.5.8, or 5.0.4 depending on your current branch
- Identify your current Moodle version from the Site Administration > Server > Environment page or admin/settings.php?section=environment
- Determine which version branch you are on (4.1.x, 4.4.x, 4.5.x, or 5.0.x)
- Back up your Moodle database and moodledata directory before proceeding
- Download the appropriate fixed release: 4.1.21 for 4.1.x branches, 4.4.11 for 4.4.x branches, 4.5.8 for 4.5.x branches, or 5.0.4 for 5.0.x branches
- Replace the existing Moodle code directory with the new version, preserving config.php and any local customizations
- Run the upgrade script by accessing your Moodle site URL (e.g., https://yoursite.com) which will trigger the database upgrade
- Verify the upgrade completed successfully by checking the version in Site Administration > Server > Environment
- Test anonymous assignment submission functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Moodle
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67857 — 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-2025-67857 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