Skip to main content
Menu
CVEs

Moodle unauthorized access to badge alignments via IDOR

CVE-2026-133067Published November 19, 2026, updated

5.4MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.5.16, 5.1.0, 5.1.9, 5.2.5, 5.3.1
Who is exposed
Not reported

Summary

Moodle has a flaw in badge alignments: missing ownership checks let a remote attacker who is logged in with badge management privileges view and change alignments on badges they do not own. The attacker could disclose data and tamper with badge configurations.

Written by a model

Original description

A flaw was found in Moodle. Due to missing ownership checks in badge alignments, an authenticated user with badge management privileges can view and modify alignments associated with badges they do not own. This vulnerability can lead to unauthorized data disclosure and tampering with badge configurations.

What to do

Upgrade to a fixed version: 4.5.16, 5.1.0, 5.1.9, 5.2.5, 5.3.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133067 (Moodle: idor in badge alignments), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133067 (entry last updated 2026-11-19):
Affected:
- moodle: fixed in 4.5.16; from 5.0.0, fixed in 5.1.0; from 5.1.0, fixed in 5.1.9; from 5.2.0, fixed in 5.2.5; from 5.3.0, fixed in 5.3.1
Fixed versions: 4.5.16, 5.1.0, 5.1.9, 5.2.5, 5.3.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133067 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133067 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2576525
- https://access.redhat.com/security/cve/CVE-2026-133067
- https://github.com/moodle/moodle/commit/27aa74ce75e6bfcdbb029640f275b5885d65ab23
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133067
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133067"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.4/10CVSS 5.4
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 5

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133067
RecordNVD · CVE-2026-133067
Write-ups 1Establishes: Technical detail and context.
Reportbugzilla.redhat.com · show_bug.cgi?id=2576525
Other links 2
RepositoryGitHub · moodle/moodle · Commit 27aa74ce
Linkaccess.redhat.com · security/cve/CVE-2026-133067

Questions about CVE-2026-133067

Is CVE-2026-133067 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133067?

moodle: before 4.5.16; from 5.0.0 before 5.1.0; from 5.1.0 before 5.1.9; from 5.2.0 before 5.2.5; from 5.3.0 before 5.3.1.

Source: cve.now feed data

How do I fix CVE-2026-133067?

Upgrade to a fixed version: 4.5.16, 5.1.0, 5.1.9, 5.2.5, 5.3.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.