Moodle Configurable Reports: Critical Vulnerabilities and How to Respond

Two CVEs hit Moodle's most widely used custom reporting plugin. Check if your LMS is exposed and how to patch without breaking administrative reports.

by Cleverson Gouvêa

Moodle Configurable Reports: Critical Vulnerabilities and How to Respond

Configurable Reports for Moodle, the custom reporting block maintained by Juan Leyva, had two security vulnerabilities published as CVEs on 10/20/2026 and was flagged on moodle.org's security advisory list as a critical issue. If your LMS relies on this plugin, any authenticated user could be just one click away from reading confidential student records. Below, I break down how to verify whether your environment is affected, how to upgrade without disrupting departmental reporting, and when to migrate to Moodle's native report builder.

TL;DR

  • CVE-2026-113607 (authorization bypass via the web service block_configurable_reports_get_report_data): patched in plugin version 5.3.0.
  • CVE-2026-113608 (SQL injection in viewreport.php via the filter_var parameter): patched in 5.3.1. Allows attackers to dump database tables, including password hashes.
  • Subsequent releases include 5.3.2 (11/01/2026, complete plugin security overhaul) and 5.3.3 (11/10/2026). The current secure target is 5.3.3.
  • The 5.3.x release series belongs to the plugin, not Moodle core. Version 5.3.3 requires Moodle 4.0+ and PHP 8.0+.
  • Version 5.3.2 changes the behavior of %%FILTER_VAR%% and SQL sanitization. Legacy queries will likely fail. Always test in staging first.

What Happened with Configurable Reports for Moodle

I am Cleverson Gouvêa, CTO at Agathas Web. I have managed Moodle environments since Configurable Reports was practically the only viable way to deliver tailored academic and operational reports without building a custom plugin from scratch. That is why this block is embedded across so many legacy enterprise and campus installations: a sysadmin installed it in 2015, created twenty custom SQL queries, and nobody has touched it since.

Here is the confirmed timeline from public security advisories:

Date Release Event Source
10/19/2026 Plugin versions 5.3.0 and 5.3.1 published on GitHub Official plugin repository
10/20/2026 CVE-2026-113607 and CVE-2026-113608 officially published CVE Registry / NVD
11/01/2026 Version 5.3.2 released, delivering comprehensive security refactoring Version 5.3.2 Release Notes
11/10/2026 Version 5.3.3 released with stricter custom SQL constraints Version 5.3.3 Release Notes

Regarding the moodle.org advisory: the Moodle security advisory page classifies this flaw in the third-party plugin block_configurable_reports as critical. The advisory notes that the maintainer submitted a patched release to the plugin directory and recommends upgrading immediately, or disabling/uninstalling the block until a patch can be applied. Installations without this plugin require no action. While briefing notes cite 11/10/2026 as the advisory release date, automated access limits prevent real-time verification of that specific timestamp; what is confirmed is that version 5.3.3 officially launched on 11/10/2026.

A vital point for stakeholder briefings: the moodle.org advisory is an official alert concerning a third-party community plugin. Moodle core remains unaffected. The responsibility for securing and patching the deployment lies entirely with the hosting institution.

The Two CVEs Explained in Plain Terms

CVE-2026-113607: Restricted Reports Exposed to Any Logged-In User

The plugin registers a web service endpoint named block_configurable_reports_get_report_data. When permission checks failed, the function merely logged a warning and returned the requested tabular dataset anyway. In practice, any authenticated user could pass a report ID and view the output—including confidential queries detailing student rosters, grades, and faculty data. This broken access control vulnerability (CWE-863) was resolved in 5.3.0. CVSS 3.1 rates it at 6.5, and CVSS 4.0 places it at 7.1, according to the entry on OpenCVE.

CVE-2026-113608: SQL Injection via filter_var

Custom SQL reports in the plugin support the token %%FILTER_VAR%%, which ingests query parameters directly from the URL. Inside report_sql::prepare_sql(), this input was concatenated into database queries without proper parameterization. A low-privileged user with read permissions on a filtered report could inject subqueries or execute a UNION SELECT to exfiltrate database contents, including password hashes and session keys. This classic SQL injection flaw (CWE-89) was patched in 5.3.1. It carries a CVSS 3.1 score of 5.3 and a CVSS 4.0 score of 6.0 on the official CVE-2026-113608 record.

Why a "Medium" Base Score Prompts a Critical Enterprise Alert

Standard CVSS scores rate these flaws as medium severity because an attacker must have an active session. In an educational LMS or corporate training portal, however, every student, contractor, and employee has valid login credentials. When an institution serves tens of thousands of active enrollments, authentication is zero barrier to entry. The data exposed touches precisely what federal and state privacy statutes—such as FERPA, CCPA, and state data breach laws—strictly mandate protecting: student names, institutional emails, Social Security numbers or custom identifiers, transcripts, and attendance records. While no active weaponization was publicly documented as of 11/22/2026, waiting to patch is an unnecessary enterprise risk.

How to Check If Your LMS Runs Configurable Reports

Auditing your LMS takes less than five minutes and requires no root server access.

  1. Log in as an administrator and navigate to Site administration > Plugins > Plugins overview.
  2. Click on Additional plugins and search for "Configurable Reports" (component: block_configurable_reports).
  3. Check the version column. If Configurable Reports is running anything lower than 5.3.1, your platform is exposed to both vulnerabilities. If it is below 5.3.3, you lack the full security hardening suite.

If you have direct database access, these two queries clarify your risk profile immediately (replace mdl_ with your 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 query identifies the active codebase version. The second reveals your total report footprint and highlights raw SQL reports, where injection attack surfaces are concentrated.

On your filesystem, the plugin resides at blocks/configurable_reports. In Moodle 5.1 and newer distributions using the updated structure, check public/blocks/.

The Trap: Hidden Blocks Are Not Disabled Blocks

Administrators often assume that hiding a block from course layouts neutralizes the risk. Hiding the UI element does not deactivate the underlying code. So long as the directory exists in your installation, viewreport.php and the associated web services remain live and directly queryable via predictable URLs.

How to Patch the Plugin Without Production Downtime

Deploying this security update requires the disciplined staging workflow we implement across enterprise Moodle environments. For an extensive look at managing dependency baselines, refer to our guide on essential Moodle plugins and version compatibility; the specific protocol for this patch follows below.

Step-by-Step Remediation Plan

  1. Execute a verified full backup: database snapshot, moodledata directory, and web root. Never run an upgrade without a restorable fallback.
  2. Replicate into staging: spin up an exact clone of production on an isolated staging server matching your production PHP runtime and Moodle build.
  3. Download version 5.3.3 from the official Moodle plugin directory or the maintainer's GitHub release page. Verify your stack meets the prerequisites: Moodle 4.0+ and PHP 8.0+.
  4. Deploy updated files to the plugin folder and execute the database migration via the admin GUI or CLI: php admin/cli/upgrade.php.
  5. Smoke-test every SQL query in your staging instance. Catalog every report that throws execution errors (see syntax changes below).
  6. Refactor broken queries, secure sign-off from departmental stakeholders, and schedule production deployment during an approved maintenance window.

If your web tier is running an outdated PHP runtime, review our analysis of the November PHP security updates. Patching an application-tier plugin while neglecting end-of-life server dependencies leaves critical attack vectors wide open.

Breaking Changes in Versions 5.3.2 and 5.3.3

The maintainer introduced strict SQL parsing mechanisms to eliminate recurring injection vectors, which will break legacy custom queries:

  • %%FILTER_VAR%% now binds strictly as a parameterized value, not raw SQL fragments. Reports injecting dynamic conditional operators via URL parameters must move logic inside the statement (e.g., AND u.city = %%FILTER_VAR%%).
  • When "SQL Security" is enabled, keyword and semicolon validation executes at runtime. Imported or legacy scripts containing inline termination or nested queries may fail automatically.
  • Version 5.3.3 mandates read-only operations: queries must begin strictly with SELECT or WITH. Command prefixes such as EXEC, EXECUTE, and UESCAPE are permanently blocked.
  • Columns storing sensitive credentials (passwords, secrets, session keys) can no longer be rendered in results or used in report filters.
  • Appending ?debug=1 now displays raw SQL output exclusively to administrators holding custom query creation capabilities.
  • Automated email triggers now validate that recipients are actively enrolled users inside the respective course context.
  • Scheduled background exports transition to Moodle's native task scheduler, eliminating dependencies on legacy block cron jobs.

In short: upgrading is non-negotiable, but pushing this update blind on a Friday evening is a surefire way to break mission-critical administrative dashboards by Monday morning.

When to Disable Rather Than Upgrade

Immediate patching is not always feasible. For instance, legacy instances on Moodle 3.x cannot run version 5.3.3 due to core framework requirements. If you cannot patch immediately, follow the advisory's secondary directive: lock down or uninstall the block until infrastructure updates can be performed.

Disabling the Plugin While Preserving Stored Queries

  • Revoke capabilities: navigate to Site administration > Users > Permissions > Define roles, and strip block/configurable_reports:viewreports from every role except Site Administrator.
  • Audit external web services: if your platform integrates mobile apps, external portals, or an ERP, go to Site administration > Server > Web services > External services and ensure no public token exposes plugin endpoints.
  • Hide the block instance under Plugins > Blocks > Manage blocks. While insufficient on its own, it removes intuitive surface areas when combined with strict capability revocation.

When Complete Uninstallation Makes Sense

If your audit shows zero report usage over the past two quarters, deprecate the tool entirely. Uninstalling via the plugin administrative screen drops the block_configurable_reports database table; export and archive your SQL queries beforehand. After uninstalling, remove the physical directory from the server to prevent Moodle from prompting a reinstallation on the next administration page load.

When NOT to Uninstall

Do not pull the plugin in a panic if academic operations, financial aid tracking, or regulatory reporting depend on its output. Revoke non-admin access, patch in staging, and migrate queries methodically. Deleting the plugin without backing up definitions permanently erases years of institutional reporting logic built by teams who may no longer work at your organization.

Post-Patch Audit: Hardening Permissions and Query Security

Applying the update fixes known CVEs, but it does not prevent an internal user with elevated permissions from drafting queries that expose sensitive PII. A complete permissions audit is essential.

Core Permissions and Associated Risk Profiles

Capability Default Allocation Documented Plugin Risk
block/configurable_reports:managesqlreports None (Locked) PII exposure, XSS injection, config drift, data destruction
block/configurable_reports:managereports Manager Unsolicited messaging, PII exposure
block/configurable_reports:manageownreports Manager PII exposure, spam vectors, XSS injection
block/configurable_reports:viewreports Manager PII exposure
block/configurable_reports:addinstance Editing Teacher, Manager Spam vectors, XSS injection

Notice that in a standard installation, managesqlreports is unassigned by default. If your environment grants instructor or department coordinator roles this capability, an administrator customized permissions previously. Use Site administration > Users > Permissions > Check system permissions to confirm which accounts hold raw SQL authoring rights.

Hardening Checklist

  • Global Reports (the global flag in report settings): review audience boundaries to verify who can access cross-course datasets.
  • Reports utilizing %%FILTER_VAR%%: refactor them to use strict equality parameters and test unexpected string inputs.
  • Wildcard queries (SELECT *) targeting user tables: replace them with explicit field lists. Never include credential attributes such as password or token fields.
  • "Allowed SQL users" (allowedsqlusers): restrict custom SQL execution solely to vetted database engineers or sysadmins.
  • Remote database connections (dbhost, dbuser, dbpass): if configured to run against external data warehouses or replicas, confirm the database credentials provide strictly read-only access.
  • External Report Repository (crrepository): fetching reporting templates from community repositories executes untrusted SQL; inspect every script manually prior to deployment.

To implement comprehensive baseline controls across your infrastructure, refer to our complete Moodle server hardening checklist covering firewalls, PHP execution constraints, and file system permissions.

The Native Moodle Report Builder: An Enterprise Alternative

Beginning with Moodle 4.0, the core platform provides an integrated Report Builder located at Site administration > Reports > Report builder > Custom reports. For modern academic analytics and compliance dashboards, this native tool has rendered legacy third-party report blocks obsolete.

Feature Comparison

Feature Configurable Reports (Plugin) Report Builder (Core)
Maintenance Authority Individual community volunteer Moodle HQ core engineering team
Security Patching Dependent on external maintainer Addressed through routine Moodle core releases
Direct SQL Writing Yes (high flexibility, high risk) No (governed data entities)
Visual Query Builder Basic / legacy interface Modern UI with structured sources, filters, and dynamic conditions
Audience Access Control Granular plugin-level capabilities Customizable per-report audience permissions
Automated Schedules Custom block cron tasks Native scheduled tasks with audience distribution
Sensitive Table Exposure Risk High (if SQL lacks strict sanitation) Low (constrained strictly to authorized entities)

When to Migrate to Core Reporting

  • Your data requirements align with standard core sources: users, courses, cohort enrollments, activity completion, gradebooks, and competencies.
  • Your team lacks dedicated database administrators to continuously audit and maintain custom SQL queries.
  • Your organization aims to minimize third-party technical debt to simplify future Moodle LTS upgrades.

When Configurable Reports Remains Necessary

  • Complex aggregations involving deep transactional logs, custom user metadata fields, and bespoke multi-table relationships not yet supported by core data sources.
  • Automated feeds providing direct exports into legacy external systems (SIS, ERP, or payroll platforms).

In those scenarios, you have two sustainable paths: keep Configurable Reports fully patched with locked-down execution privileges, or build a custom core report source that extends Moodle's native Report Builder API. The latter incurs an upfront development investment but eliminates external plugin vulnerability cycles during core upgrades. For an example of how Moodle core expands analytical capabilities, see our deep dive on the AI usage reporting framework in Moodle 5.3.

Realistic Costs and Delivery Timelines

Because every environment carries a unique inventory of custom SQL statements, remediation efforts cannot follow a generic flat-rate model. However, enterprise engagements typically follow this structured scope:

  • Security Audit & Discovery (version checks, active report inventories, permission matrices): 2 to 4 business hours.
  • Staging Deployment and Core Patching (environments with under 15 standard queries): 1 business day, including verifiable snapshots and validation.
  • Refactoring Syntax Errors (Breaking changes in %%FILTER_VAR%%): variable depending on complexity. Basic filtering adjusts quickly; complex URL-based conditional scripts require rewriting logic.
  • Migration to Core Report Builder: timeline depends on the number of reports transitioning into standard core entities versus those requiring custom data source development.

Organizations working through our Agathas Web Moodle consulting services receive a detailed audit and remediation estimate itemized per query. The cost of proactive patching is minimal compared to managing a FERPA violation, notifying state attorneys general of an unauthorized data breach, and managing the operational fallout of compromised student records.

How Agathas Web Resolves the Threat

Our engineering team holds Moodle Developer Certifications through the Moodle Academy and operates directly within Moodle's core architecture, PHP runtimes, and relational database layers. When institutions contact us to address these vulnerabilities, we execute a standardized response protocol.

Our Comprehensive Deliverables Include:

  • Full platform security assessment: Moodle core release status, PHP lifecycle health, and a zero-trust audit of all third-party plugins.
  • Pre-change staging replication and verified automated system snapshots.
  • Production deployment of release 5.3.3 alongside unit testing of all active reporting pipelines.
  • Refactoring of legacy SQL statements invalidated by security constraints in 5.3.2 and 5.3.3.
  • Complete role permission hardening, accompanied by a documented remediation report detailing previously open attack surfaces.
  • Strategic reporting roadmap: categorizing reports to retain in the plugin, migrate to the core Report Builder, or transition to custom enterprise data sources.

Our Engagement Workflow: We begin with an initial technical review, issue a transparent statement of work covering scope, deliverables, and timelines, and deploy fixes strictly during scheduled maintenance windows agreed upon by your IT operations team.

Engagement Models: Access our expertise via dedicated Moodle development and support services for a rapid single-incident remediation, or engage us through an annual SLA support retainer covering continuous vulnerability monitoring, core and plugin upgrades, and disaster recovery validation. If your team is unsure of your current exposure, request our technical diagnostic today to confirm your security posture.

Next Steps: Patch, Audit, and Modernize

Configurable Reports remains a capable tool, and the open-source maintainer responded responsibly by deploying versions 5.3.0 and 5.3.1 prior to public CVE disclosure, followed by robust security hardening in versions 5.3.2 and 5.3.3. However, software updates only solve code-level bugs; they cannot fix decade-old installations running with unvetted permissions and unmonitored SQL statements.

Your action plan is clear: audit your active plugin version today, restrict public reporting endpoints immediately if an update cannot be applied right away, patch through an isolated staging pipeline, and establish a roadmap toward Moodle's native Report Builder. To execute this upgrade safely and securely, reach out to the enterprise Moodle team at Agathas Web.