# CVE-2026-113607: Configurable Reports block for Moodle before 5.3.0 Authorization Bypass via get_report_data


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-7v7c-h53q-gqrm

## What is CVE-2026-113607?

CVE-2026-113607 is a high-severity vulnerability in jleyva moodle-block_configurablereports, published on 20 Oct 2026. 

### Official description

Configurable Reports block for Moodle before 5.3.0 contains an authorization bypass vulnerability that allows authenticated users to read restricted reports through the block_configurable_reports_get_report_data web service. When check_permissions fails, the function only adds a warning and still returns the full report table, letting any logged-in user supply arbitrary report ids to read SQL reports over user and grade data.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-113607 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113607 is a high-severity vulnerability in jleyva moodle-block_configurablereports, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113607 in the wild and no public exploit code.

Affected product: jleyva moodle-block_configurablereports. 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-113607/ (Markdown: https://insights.sbomify.com/CVE-2026-113607/index.md)
```

## Sources

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

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