William Desportes

**Name of the Vulnerable Software and Affected Versions** phpMyAdmin versions 4.9 through 4.9.7 phpMyAdmin versions 5.1 through 5.1.1 **Description** A valid user who is already authenticated to phpMyAdmin can manipulate their account to bypass two-factor authentication for future login instances. This issue is related to how phpMyAdmin processes two-factor authentication. **Recommendations** For phpMyAdmin versions 4.9 through 4.9.7, update to version 4.9.8 or later to resolve the issue. For phpMyAdmin versions 5.1 through 5.1.1, update to version 5.1.2 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** phpMyAdmin versions prior to 4.9.2 **Description** A SQL injection attack can be triggered through the designer feature by using a crafted database or table name. **Recommendations** For versions prior to 4.9.2, update to version 4.9.2 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** phpMyAdmin versions prior to 4.9.0.1 **Description** The issue is related to a specially crafted database name that can trigger an SQL injection attack through the designer feature. This is due to the lack of protection measures for the SQL query structure in the designer feature, specifically in the move.js file. An attacker can exploit this to execute arbitrary code remotely. **Recommendations** For versions prior to 4.9.0.1, update to version 4.9.0.1 or later to resolve the issue. As a temporary workaround, consider disabling the designer feature until a patch is available. Restrict access to the move.js file to minimize the risk of exploitation. Avoid using specially crafted database names in the affected feature until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** phpMyAdmin versions prior to 4.8.2 **Description** A Cross-Site Scripting issue has been found where an attacker can use a crafted database name to trigger an attack when that database is referenced from the Designer feature. The issue is related to the `js/designer/move.js` file. **Recommendations** For versions prior to 4.8.2, update to version 4.8.2 or later to resolve the issue. As a temporary workaround, consider restricting access to the Designer feature until the update is applied.