# CVE-2026-133071: Moodle: idor in lesson page editing allows moving pages from other courses


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-26fp-cwcq-7j4p

## What is CVE-2026-133071?

CVE-2026-133071 is a medium-severity vulnerability in moodle, published on 19 Nov 2026. 

### Official description

A flaw was found in Moodle. Due to a missing authorization check when editing Lesson activity pages, authenticated users with teacher privileges can view and move lesson pages from courses they are not permitted to access into their own lessons. This issue can lead to unauthorized access and modification of restricted course content.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-133071?


## How do I fix CVE-2026-133071?

No fix has been published for CVE-2026-133071 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-133071 being exploited?

There is no known exploitation of CVE-2026-133071 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133071 and fix it if it is affected.

What it is: CVE-2026-133071 is a medium-severity vulnerability in moodle, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133071 in the wild and no public exploit code.

Affected product: moodle. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-133071/ (Markdown: https://insights.sbomify.com/CVE-2026-133071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133071
- OSV: https://osv.dev/vulnerability/CVE-2026-133071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133071/
Summaries are generated and may contain mistakes; the official description above is the record.
