CVE-2026-113607 jleyva CVE debrief

Who should care

Moodle administrators, security teams, and users with access to sensitive reports should be aware of this vulnerability and take necessary actions to mitigate it. They should prioritize updating to version 5.3.0 or later and review access to sensitive reports. Additionally, they should ensure proper authorization checks are in place to prevent unauthorized data exposure.

Why it matters

The Configurable Reports block for Moodle before version 5.3.0 contains an authorization bypass vulnerability, allowing authenticated users to read restricted reports. Moodle administrators and security teams should prioritize updating to version 5.3.0 or later and review access to sensitive reports.

• Authenticated users can read restricted reports, potentially leading to unauthorized data exposure.
• The vulnerability can be exploited by supplying arbitrary report IDs to read SQL reports over user and grade data.
• Moodle administrators need to update to version 5.3.0 or later to mitigate this vulnerability.

Technical summary

The Configurable Reports block for Moodle before version 5.3.0 contains an authorization bypass vulnerability. This allows authenticated users to read restricted reports through the block_configurable_reports_get_report_data web service. The vulnerability arises when the check_permissions function fails, adding a warning but still returning the full report table. This enables any logged-in user to supply arbitrary report IDs to read SQL reports over user and grade data. Affected Moodle deployments should prioritize updating to version 5.3.0 or later to mitigate this vulnerability.

Defensive priority

Moodle administrators and security teams should prioritize updating to version 5.3.0 or later to mitigate this vulnerability. Additionally, reviewing and restricting access to sensitive reports and ensuring proper authorization checks are in place can help prevent unauthorized data exposure.

Recommended defensive actions

• Update Moodle to version 5.3.0 or later
• Review and restrict access to sensitive reports
• Ensure proper authorization checks are in place
• Confirm whether affected Moodle deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and source item provide details about the vulnerability, including its description, affected versions, and references to patches and advisories. However, there is limited information on potential exploitation or specific attacks.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.