Moodle versions 4.2.0 through 5.3.0 contain a missing authorization check in the core_grades_get_gradeitems web service. This flaw allows authenticated course users, such as enrolled students, to view grade items that are normally hidden from them by the gradebook. The vulnerability affects multiple Moodle releases and has been fixed in version 5.3.1.
Moodle versions 4.2.0 through 5.3.0 contain an information disclosure vulnerability in the core_grades_get_feedback web service. This flaw allows non-editing teachers to access grade feedback and user identity information, including email addresses, from other groups due to missing group-membership and enrolment checks. The issue is fixed in version 5.3.1.
Moodle versions up to 5.3.0, including 5.2.4, 5.1.8, 5.0.11, and 4.5.15, contain an SQL injection vulnerability in the External database enrolment plugin via the course idnumber field. This flaw allows editing teachers to inject a payload that executes during scheduled synchronization with MySQL/MariaDB external databases, potentially reading data and manipulating enrolment results. The vulnerability is fixed in Moodle 5.3.1.
Moodle versions up to 5.3.0, including specific subversions of 5.2, 5.1, 5.0, and 4.5, contain a path traversal vulnerability in the Blackboard question import feature. This flaw allows teachers with import or lesson edit permissions to upload crafted zip files that exploit directory traversal sequences to copy sensitive server files such as config.php into their draft area.
Pillow versions prior to 13.0.0 contain a vulnerability in the libtiff TIFF encoder where crafted TIFF tags can cause invalid memory reads or process crashes. This occurs when attacker-controlled image metadata is saved, potentially leading to disclosure of process memory if the encoded output is returned to an attacker. The issue affects operations that re-save compressed TIFF images or convert images preserving EXIF metadata into compressed TIFF output. The vulnerability is fixed in Pillow 13.0.0.
Pillow versions 2.3.0 through 12.3.0 contain a vulnerability in EPS rendering where scaled image dimensions are not validated before invoking Ghostscript. This can lead to excessive CPU and disk resource consumption by Ghostscript when processing untrusted EPS or PostScript files with an application-selected scale greater than one. The decompression bomb protection only checks the scaled output after rendering, allowing resource usage beyond configured limits. This issue is fixed in Pillow version 13.0.0.
ProxySQL versions prior to 3.0.10, 3.1.10, and 4.0.10 contain a vulnerability in the MySQL compressed packet decompression function. An authenticated MySQL client negotiating compression can manipulate the payload length, causing ProxySQL to read uninitialized heap memory and forward stale data to the backend. This can lead to disclosure of prior SQL queries, result data, credentials, or session state, and may also cause excessive memory allocations. The issue is fixed in versions 3.0.10, 3.1.10, and 4.0.10.
Prometheus versions through 3.15.1 have a credential leak vulnerability where attackers can capture Azure AD or Google IAM bearer tokens by exploiting remote_write request redirects. An attacker controlling the remote-write endpoint or a redirecting server can issue a 3xx redirect to their own host and replay the token, potentially writing metrics to the victim's backend.
phpMyAdmin versions up to 5.2.3 have a stored cross-site scripting (XSS) vulnerability in the Designer query history feature. Database users with CREATE privileges can inject malicious scripts via specially crafted table names containing HTML markup. When another user interacts with the Designer query mode and adds a condition on such a table, the injected script executes in their session.
phpMyAdmin versions up to 5.2.3 have an SQL injection vulnerability in the /database/central-columns endpoint. Authenticated users can exploit this by supplying unescaped values in the col_extra and col_attribute parameters. This allows injection into INSERT and UPDATE queries executed with controluser privileges, potentially enabling unauthorized reading or modification of other users' configuration-storage data.
phpMyAdmin versions up to 5.2.3 have an authentication bypass vulnerability in the WebAuthn two-factor authentication implementation. The flaw exists in CustomServer::parseAndValidateAssertionResponse(), which fails to verify WebAuthn assertion signatures against stored public keys. An attacker who already has a victim's MySQL credentials can exploit this by sending a crafted WebAuthn response with matching challenge, origin, and rpIdHash to bypass the second factor and gain unauthorized database access.
phpMyAdmin versions up to 5.2.3 have a vulnerability that allows authenticated attackers to remove two-factor authentication (2FA) by sending a specially crafted request to the /config/set endpoint. This missing re-authentication flaw enables attackers with a hijacked session to disable 2FA, reducing login security to just the MySQL password.
phpMyAdmin versions up to 5.2.3 contain a server-side request forgery (SSRF) vulnerability in setup/validate.php. This vulnerability allows unauthenticated attackers to send POST requests with attacker-controlled host and port parameters, triggering outbound MySQL-protocol connections. The lack of a setup-disabled guard in this endpoint enables attackers to probe internal ports by analyzing error messages returned from Validator::testDBConnection().
phpMyAdmin versions up to 5.2.3 contain an SQL injection vulnerability in the Designer saveSetting() function. Authenticated users can exploit this flaw by sending crafted parameters to the /database/designer endpoint, potentially overwriting other users' designer settings or executing controluser subqueries.
phpMyAdmin versions up to 5.2.3 have a cross-site request forgery (CSRF) vulnerability that allows attackers to bypass CSRF token checks on non-AJAX POST requests to the /sql or /database/sql endpoints. This enables remote attackers to execute arbitrary SQL commands with the privileges of an authenticated user by tricking them into submitting crafted POST requests. The vulnerability affects configurations using HTTP or config authentication.
Parse Server versions from 9.7.0 up to but not including 9.10.5 contain an authorization flaw involving installation update misdirection via the X-Parse-Installation-Id header. This flaw allows attackers who know another installation's object ID to trigger protected field processing on that installation while writing data elsewhere, when the protectedFieldsTriggerExempt feature is enabled. The issue is fixed in version 9.10.5.
Parse Server versions from 9.7.0 up to but not including 9.10.5 have an information disclosure vulnerability. This flaw allows clients with create or update permissions to read protected field values written by beforeSave triggers when the protectedFieldsSaveResponseExempt setting is false. The issue arises because clients can access these protected fields using dot notation keys in the same request. The vulnerability is fixed in version 9.10.5.
Parse Server versions before 8.6.108 and from 9.0.0 up to but not including 9.10.5 contain a prototype pollution vulnerability. This flaw allows clients with class write access to send specially crafted keys that corrupt built-in object functions, leading to denial of service by causing all requests to fail until the server is restarted.
Parse Server versions before 8.6.106 and versions 9.0.0 up to but not including 9.10.5 mishandle dot notation keys with null or undefined values during object saving. This causes writes to be stored but returns an error that skips afterSave triggers and LiveQuery events. Exploiting this flaw allows a client with write access to bypass audit logging, notifications, and derived data updates.
Parse Server versions before 8.6.107 and from 9.0.0 up to but not including 9.10.5 have an information disclosure vulnerability. This occurs because the server returns the stored value of a field reverted by a beforeSave trigger in object update responses, even to clients without read access to that object or field. An authenticated client able to update such an object can read protected values, including its own account's raw MFA authData when the protectedFieldsTriggerExempt feature is enabled.