Configurable Reports for Moodle: Critical Security Vulnerabilities and Remediation
Two critical CVEs have hit Moodle’s most popular reporting plugin. Discover whether your VLE is exposed and how to remediate without breaking faculty reports.
by Cleverson Gouvêa

Configurable Reports Moodle, the custom reporting block maintained by Juan Leyva, had two security vulnerabilities published as CVEs on 20/10/2026 and was subsequently listed on moodle.org’s security advisory board as a critical issue. If your VLE relies on this plugin, any authenticated user could be a single crafted link away from accessing data they should never see. Below, I outline how to confirm whether your institution is exposed, how to patch safely without disrupting academic registry reporting, and when to consider migrating to Moodle’s native Report Builder.
TL;DR
- CVE-2026-113607 (broken authorisation bypass via the web service
block_configurable_reports_get_report_data): resolved in version 5.3.0 of the plugin.- CVE-2026-113608 (SQL injection in
viewreport.phpvia thefilter_varparameter): resolved in 5.3.1. Allows arbitrary database reads, including password hashes.- These were followed by 5.3.2 (01/11/2026, an exhaustive security audit of the entire plugin) and 5.3.3 (10/11/2026). Currently, your deployment target should be 5.3.3.
- The 5.3.x numbering belongs to the plugin, not Moodle core. Version 5.3.3 requires Moodle 4.0 or above, running on PHP 8.0 or later.
- Version 5.3.2 changes the behaviour of
%%FILTER_VAR%%and SQL sanitisation checks. Legacy queries will likely fail. Always test in a staging environment first.
What happened to Configurable Reports Moodle
I am Cleverson Gouvêa, CTO at Agathas Web. I have administered Moodle environments since the era when Configurable Reports was essentially the only way to deliver bespoke queries for academic registry teams and course directors without developing custom code. That is precisely why Configurable Reports Moodle sits in so many long-standing UK university and college VLEs: an administrator installed it back in 2015, wrote twenty SQL queries, and nobody has touched the codebase since.
The confirmed public disclosure timeline is as follows:
| Date | Release / Event | Source |
|---|---|---|
| 19/10/2026 | Plugin versions 5.3.0 and 5.3.1 published to GitHub | Official plugin repository |
| 20/10/2026 | CVE-2026-113607 and CVE-2026-113608 officially published | CVE / NVD databases |
| 01/11/2026 | Version 5.3.2 released, providing comprehensive security patches across the plugin | 5.3.2 release notes |
| 10/11/2026 | Version 5.3.3 released, enforcing stricter constraints on custom SQL execution | 5.3.3 release notes |
Regarding the moodle.org advisory: the Moodle security advisory page published a notice categorising this vulnerability in the third-party plugin block_configurable_reports as critical. It confirms that the maintainer uploaded a patched release to the plugins directory, advising administrators to upgrade immediately or disable/uninstall the block in the interim. If your site does not have the plugin installed, no action is required. The brief for this alert references 10/11/2026 as the notice date. I was unable to verify the exact page timestamp directly (due to automated access restrictions), but what is confirmed is that version 5.3.3 was released on precisely 10/11/2026.
A crucial distinction when briefing senior leadership: the moodle.org advisory is an official notice regarding a third-party plugin. Moodle core is entirely unaffected. The governance and patching liability rests solely with the platform owner who installed the plugin.
The two CVEs explained without unnecessary jargon
CVE-2026-113607: restricted reports accessible by any logged-in user
The plugin registers a web service named block_configurable_reports_get_report_data. When an authorisation check failed, the code merely logged a debugging warning but returned the full report payload regardless. In practice, any logged-in student or guest could submit a report ID and retrieve its contents—including sensitive SQL reports covering user records, enrolments, and assessment grades. This is an improper authorisation flaw (CWE-863), patched in 5.3.0. It carries a CVSS 3.1 score of 6.5 and CVSS 4.0 of 7.1, according to OpenCVE.
CVE-2026-113608: SQL injection via filter_var
Custom SQL reports in the plugin accept the %%FILTER_VAR%% placeholder, which pulls an arbitrary value straight from URL parameters. Within report_sql::prepare_sql(), this value was concatenated into the active query without adequate parameterisation or sanitisation. A low-privilege user with access to view a filtered report could inject subqueries or a UNION SELECT payload to extract any table from the database—including administrative password hashes. This is textbook SQL injection (CWE-89), resolved in 5.3.1. It holds a CVSS 3.1 score of 5.3 and CVSS 4.0 of 6.0 on the CVE-2026-113608 advisory entry.
Why a "medium" CVSS rating prompted a "critical" warning
The CVSS base metrics fall in the medium band because exploitation requires an authenticated account. However, in a higher education VLE, thousands of students are constantly logged in. "Requires authentication" is no security perimeter at all. Furthermore, the accessible data represents precisely what the UK GDPR and Data Protection Act 2018 require organisations to protect: full names, corporate email addresses, National Insurance numbers stored in custom profile fields, course grades, and attendance metrics. As of 22/11/2026, I have seen no public reports of active in-the-wild exploitation, but that is never a reason to delay patching.
How to check if your VLE is running Configurable Reports Moodle
Auditing your VLE takes under five minutes and does not require command-line access to the host server.
- Log in with Site Administrator privileges and navigate to Site administration > Plugins > Plugins overview.
- Select the Additional plugins tab and search for "Configurable Reports" (component identifier:
block_configurable_reports). - Inspect the installed version column. If Configurable Reports displays a version lower than 5.3.1, you are vulnerable to both CVEs. If it is below 5.3.3, you are missing critical query-hardening patches.
If you have direct access to your database instance, two queries will immediately clarify your exposure (replace mdl_ with your local table prefix):
SELECT value FROM mdl_config_plugins
WHERE plugin = 'block_configurable_reports' AND name = 'release';
SELECT COUNT(*) AS total, SUM(CASE WHEN type = 'sql' THEN 1 ELSE 0 END) AS sql_reports
FROM mdl_block_configurable_reports;
The first statement identifies the exact release deployed. The second reveals the total volume of reports and how many rely on raw SQL, which represents the highest structural risk.
On your filesystem, the directory resides under blocks/configurable_reports. For Moodle 5.1 onwards adopting the updated directory layout, inspect public/blocks/.
The trap: disabled blocks that remain active
Administrators frequently attempt to "deactivate" the plugin by simply hiding the block from course pages. Hiding a block does not unload the underlying codebase. As long as the directory exists and the plugin is registered in Moodle’s schema, viewreport.php and the associated web services remain accessible via direct URL requests.
Safely patching the plugin
When updating Configurable Reports Moodle, follow the exact rigour required for any production-critical plugin. I cover staging methodology in detail in our guide on essential Moodle plugins and compatibility; here is the operational workflow.
Step-by-step upgrade plan
- Full system backup: take a complete snapshot of your database,
moodledata, and application code. Never apply updates without verified restoration points. - Clone to staging: mirror the production environment to an isolated staging server matching identical Moodle and PHP minor versions.
- Obtain version 5.3.3 from the official Moodle Plugins Directory or the upstream repository. Verify that your environment runs Moodle 4.0+ and PHP 8.0+.
- Replace plugin assets on the filesystem and execute the database upgrade via Site administration > Notifications or via CLI using
php admin/cli/upgrade.php. - Execute every custom SQL report within your staging instance to identify syntax or logic failures (detailed below).
- Refactor broken queries, sign off the results with academic administrators, and execute the deployment during a planned maintenance window.
If your underlying server stack is running an unsupported PHP runtime, consult our briefing on the PHP security update roundup. Securing an individual Moodle plugin while leaving an exposed PHP interpreter achieves very little.
Breaking changes introduced in 5.3.2 and 5.3.3
The release notes for versions 5.3.2 and 5.3.3 document specific security restrictions that will cause legacy queries to fail:
%%FILTER_VAR%%is strictly evaluated as a value, not arbitrary SQL syntax. Reports that injected dynamic SQL clauses via URL parameters must be refactored to embed the condition directly in the query body, such asAND u.city = %%FILTER_VAR%%.- Strict SQL Security mode: keyword blacklists and semicolon checks are now evaluated at runtime execution. Older imported reports violating these rules will immediately halt.
- Read-only custom SQL in 5.3.3: queries must begin exclusively with
SELECTorWITH. Direct statements invokingEXEC,EXECUTE, orUESCAPEare blocked. - Prohibited fields: columns containing password hashes, secrets, or session keys (
sesskey) can no longer be rendered in output tables or targeted in query filters. - Debugging restrictions: the
?debug=1parameter is now restricted solely to users with explicit SQL management permissions. - Scheduled email alerts: automated emails are now dispatched solely to active users formally enrolled on the relevant course.
- Task scheduling: recurring SQL reports now run strictly via Moodle’s modern Scheduled Tasks framework, as legacy block cron execution has been deprecated.
Upgrading is essential, but applying these patches unannounced on a Friday evening is a surefire way to break Monday morning retention tracking for the registry.
When to disable rather than update
Immediate remediation is not always feasible. For instance, institutions still maintaining legacy Moodle 3.x instances cannot run version 5.3.3, which requires Moodle 4.0. In such circumstances, the official advice holds: disable access or fully uninstall the plugin until a broader platform upgrade can be scheduled.
Disabling access without losing report definitions
- Revoke permissions immediately: navigate to Site administration > Users > Permissions > Define roles, and strip the capability
block/configurable_reports:viewreportsfrom every role except Site Administrator. - Deauthorise web services: if your institution utilises the Moodle Mobile app or enterprise integrations, check Site administration > Server > Web services > External services to ensure no plugin functions are mapped to exposed service tokens.
- Hide the block globally via Plugins > Blocks > Manage blocks. Whilst insufficient on its own, it eliminates casual interface entry points alongside permission revoking.
When complete uninstallation makes sense
If your reporting workflows have evolved and staff haven't relied on the plugin for months, uninstall it. Removing it via Moodle’s administrative UI will drop the mdl_block_configurable_reports table, so export any business-critical SQL queries beforehand. Once completed in the UI, delete the filesystem directory to prevent Moodle prompting a reinstallation during the next administrative check.
When NOT to uninstall
Never uninstall abruptly if faculty relies on custom reports to process external exam board submissions, statutory HESA/OfS returns, or hourly tutor payroll claims. Restrict capabilities, patch in staging, and migrate queries methodically. Deleting the block drops historical SQL queries that may have taken years to construct and fine-tune.
Post-patch audit: reviewing SQL queries and capabilities
Applying the update resolves both known CVEs, but it does not mitigate the governance risk of overly permissive roles creating poorly designed queries that expose sensitive data. This post-remediation audit is frequently overlooked.
Core plugin capabilities and inherent risk
| Capability | Default Role Assignment | Declared Plugin Risk Profile |
|---|---|---|
block/configurable_reports:managesqlreports |
None (Admin only) | Personal data exposure, XSS, configuration, data loss |
block/configurable_reports:managereports |
Manager | Unsolicited communication (spam), personal data exposure |
block/configurable_reports:manageownreports |
Manager | Personal data exposure, spam, XSS |
block/configurable_reports:viewreports |
Manager | Personal data exposure |
block/configurable_reports:addinstance |
Teacher (editing), Manager | Spam, XSS |
In an out-of-the-box installation, managesqlreports is assigned to no role. If lecturers or academic administrators possess this capability within your VLE, someone granted it manually. Check Site administration > Users > Permissions > Check system permissions to confirm which accounts hold elevated privileges.
Essential query review checklist
- Global reports (flagged in the database table): verify precisely which user cohorts possess execution permissions.
- Reports utilising
%%FILTER_VAR%%: refactor them to use the updated parameterised logic and stress-test them with arbitrary characters. - Overly broad queries: eliminate
SELECT *patterns across the user table, explicitly stating necessary fields and omittingpasswordhashes entirely. - Allowed SQL users setting (
allowedsqlusers): restrict this setting to specific, vetted administrative IDs. - External database connections (
dbhost,dbuser,dbpass): if configured to query a secondary data warehouse, ensure the remote credentials use a strictly read-only role. - Shared report repositories (
crrepository): importing queries from public external repositories is equivalent to executing unvetted third-party code. Audit every imported query thoroughly.
For a complete infrastructure review, our Moodle server hardening checklist outlines best practices across firewalls, PHP execution flags, and file permissions.
Moodle’s native Report Builder: the modern alternative
Since Moodle 4.0, core incorporates a built-in Report Builder engine, located at Site administration > Reports > Report builder > Custom reports. For the vast majority of academic and administrative workflows, this eliminates the need for third-party reporting blocks altogether.
Feature comparison
| Evaluation Metric | Configurable Reports (Third-Party) | Moodle Report Builder (Core) |
|---|---|---|
| Maintenance lifecycle | Independent community maintainer | Moodle HQ (supported with core releases) |
| Security patches | Subject to plugin release cycles | Bundled with regular core minor updates |
| Raw SQL support | Yes | No (safe abstraction layer) |
| Visual UI builder | Basic / legacy interface | Modern drag-and-drop columns, filters, and conditions |
| Access governance | Block capabilities | Granular audience definitions per individual report |
| Scheduled delivery | Yes (plugin cron task) | Native automated schedules and email dispatches |
| Database exposure risk | High if queries are poorly secured | Negligible: limited strictly to defined data sources |
When to migrate to native reports
- The required metrics map cleanly to existing core data sources: users, courses, enrolments, completion tracking, gradebooks, and cohorts.
- Your internal team lacks dedicated database engineers to audit and support custom SQL.
- You are actively rationalising your plugin estate ahead of a major Moodle core upgrade.
When raw SQL remains necessary
- Bespoke reporting requiring complex relational joins across historical access logs, custom user metadata, and proprietary plugin structures.
- Direct data feeds supporting downstream enterprise systems (such as a corporate ERP or student information system).
In those scenarios, you have two options: retain Configurable Reports under strict capability oversight, or develop a bespoke native Data Source plugin for Report Builder. The latter requires an upfront development investment but significantly simplifies ongoing Moodle version upgrades. If you are exploring broader operational reporting, our piece on the Moodle 5.3 AI usage report illustrates what core data sources can achieve natively.
Project scope, costs, and remediation timelines
Remediation costs cannot be quoted as a single flat figure because engineering time correlates directly with the complexity and volume of custom SQL reports. Typical projects break down into four distinct phases:
- Initial assessment (version inventory, capability auditing, and query cataloguing): typically half a day.
- Staging and production deployment (where custom SQL reports are minimal): approximately one day of engineering, including verified snapshots and validation.
- Refactoring queries broken by
%%FILTER_VAR%%changes: variable based on complexity. Standard statements can be adapted rapidly; complex multi-table queries constructed around URL logic require restructuring. - Migration to native Report Builder: dependent on how many existing reports can be transitioned into core data sources versus those requiring custom data source development.
If required, our diagnostic assessment under Agathas Web’s Moodle support services provides a detailed cost and timeline estimate per report. The most costly outcome is inaction: an avoidable breach of student data triggers mandatory reporting to the Information Commissioner's Office (ICO) within 72 hours under UK GDPR, notification to affected individuals, and significant regulatory fallout.
How Agathas Web handles this for your institution
Our engineering team holds Moodle Developer Certification from Moodle Academy. We work directly with Moodle core APIs, PHP architecture, and database optimisations, rather than relying on brittle workarounds. When an organisation approaches us regarding Configurable Reports vulnerabilities, we deliver an end-to-end remediation process.
What the engagement includes:
- Comprehensive VLE audit: exact versions of Moodle core, PHP runtime, database engine, and third-party plugins.
- Complete database and filesystem backups, alongside the provision of an isolated staging replica.
- Controlled deployment of version 5.3.3 and rigorous functional testing of all active reporting pipelines.
- Code refactoring for all queries impacted by security breaking changes in 5.3.2 and 5.3.3.
- Granular role and capability review, complete with an executive audit report documenting vulnerabilities remediated.
- Strategic roadmap per query: maintain within the patched plugin, migrate to native Report Builder, or build bespoke core data sources.
How we engage: we initiate every project with a technical review, deliver a fixed-scope proposal covering timelines and deliverables, and perform production changes strictly within agreed low-traffic maintenance windows.
Next steps: discover our Moodle development and support services for either a standalone remediation package or ongoing retainer support. Our managed SLA contracts provide continuous security patching, quarterly backup verifications, and uptime monitoring throughout the academic year. If you are unsure of your current exposure, request an audit to confirm your VLE’s status.
Summary: patch now, audit capabilities, modernise your stack
Configurable Reports remains a capable tool, and the upstream maintainer acted promptly: 5.3.0 and 5.3.1 appeared before the CVEs were formally indexed, followed quickly by the comprehensive hardening in 5.3.2 and 5.3.3. However, software risk rarely stems from code alone. It arises from unmaintained legacy plugins, historical over-permissioning, and unmonitored SQL queries.
The corrective approach is straightforward: verify your version today, restrict capabilities if an immediate patch is impossible, test the upgrade in staging, audit your custom queries, and plan a transition to Moodle’s native Report Builder. To partner with our certified specialists, contact the Moodle technical team at Agathas Web.
Related posts

Moodle Workplace 5.3 Review: Multi-Tenancy, AI Limits and UK Business Impact
Multi-tenant unified accounts, 500-row AI limits, and an updated catalogue: what Workplace 5.3 delivers and how to replicate it on open-source Moodle.

Moodle 4.5.16 Security Flaws: Breakdown of All 13 Advisories
SQL injection, cross-course IDOR, and SCORM XSS: all 13 November security bulletins explained for UK VLE administrators.

Coassemble Moodle Integration: Is the Certified Plugin Worth It for UK Teams?
Coassemble is now a Moodle Certified Integration. We compare it against H5P, SCORM, and the native editor, covering UK GDPR compliance, technical specs, and pricing.