MoodleCMS
CVE-2025-67855
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 mooodle. A remote attacker could exploit a reflected Cross-Site Scripting (XSS) vulnerability in the policy tool return URL. This vulnerability arises from insufficient sanitization of URL parameters, allowing attackers to inject malicious scripts through specially crafted links. Successful exploitation could lead to information disclosure or arbitrary client-side script execution within the user's browser.
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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in Moodle's policy tool return URL parameter. The application fails to properly sanitize or escape user-supplied input in the URL, allowing an attacker to inject malicious JavaScript code. When a victim clicks a specially crafted link, the unsanitized payload is reflected back and executed in their browser session.
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.22>= 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Moodle installation versionCheck the Moodle version by logging into the admin dashboard and viewing the site information page, or by inspecting the version.php file in the Moodle root directory (look for the $release or $version variable).Affected if The installed version falls into any of these ranges: < 4.1.22; >= 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.
-
Verify policy tool is accessibleNavigate to the Moodle policy tool interface. Typically this is accessible via the site administration under the "Policies" or "Privacy" section, or directly at /admin/policy/ URLs. Confirm the policy acceptance pages load without errors.Affected if The policy tool functionality is enabled and accessible to users on the site.
-
Inspect policy tool return URL handlingExamine how the policy tool handles the return URL parameter. Access a policy acceptance page and look for any returnurl or redirect parameter in the URL. Check if the application properly validates or encodes this parameter before using it in the response.Affected if The application reflects the return URL parameter value back into the page without proper sanitization or encoding, allowing script injection.
-
Review server-side request validation logsCheck Moodle's server logs and any available security audit logs for suspicious requests containing script tags or encoded payloads in the policy tool return URL parameter.Affected if Malicious requests targeting the policy tool return URL parameter have been logged, indicating potential exploitation attempts.
You are affected if your Moodle version is within the vulnerable ranges AND the policy tool is enabled and the return URL parameter is not properly validated or encoded before being reflected in the response.
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.224.4.114.5.8
Apply the vendor-supplied patch or update to a version that includes proper input validation and output encoding for the policy tool return URL parameter. Implement context-appropriate output encoding and validate URL parameters against an allowlist of permitted values.
Upgrade to the fixed release for your branch: 4.1.22, 4.4.11, 4.5.8, or 5.0.4
- 1. Identify the currently installed Moodle version by checking the admin interface or version.php file in the Moodle root directory
- 2. Determine which branch your installation belongs to (4.1.x, 4.4.x, 4.5.x, or 5.0.x)
- 3. Backup your Moodle database and entire Moodle directory (including moodledata) before proceeding with any upgrade
- 4. Download the appropriate fixed version for your branch: 4.1.22, 4.4.11, 4.5.8, or 5.0.4 from moodle.org
- 5. Place the site into maintenance mode via Site Administration > Server > Maintenance Mode
- 6. Replace the Moodle code directory with the new version files, preserving your config.php and any local customizations
- 7. Run the Moodle upgrade process by accessing the site URL as an administrator
- 8. Verify the upgrade completed successfully and test that the policy tool functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67855 — 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-67855 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