An Đặng

**Nome do software vulnerável e versões afetadas** Plugin Smush para WordPress (versões afetadas não especificadas) **Descrição** O problema está relacionado à falta de uma verificação de permissão na função `delete resmush list()`, permitindo que invasores autenticados com permissões mínimas, como um assinante, excluam a lista resmush do Nextgen ou da Biblioteca de Mídia. Isso possibilita a exclusão não autorizada da lista resmush. **Recomendações** No momento, não há informações sobre uma versão mais recente que contenha uma correção para essa vulnerabilidade.

**Name of the Vulnerable Software and Affected Versions** MStore API plugin for WordPress versions up to, and including, 4.10.7 **Description** The MStore API plugin for WordPress is vulnerable to Unauthorized Account Access and Privilege Escalation due to improper implementation of the Apple login feature. This allows unauthenticated attackers to log in as any user as long as they know the user's email address. The issue was escalated to the plugin's team 30 days ago, but a patch has not yet been released. **Recommendations** For versions up to, and including, 4.10.7, consider disabling the Apple login feature until a patch is available to prevent unauthorized account access and privilege escalation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** MStore API plugin for WordPress versions up to, and including, 4.0.1 **Description** The issue allows unauthenticated attackers to perform Blind SQL Injection via the `id` parameter due to insufficient escaping on user-supplied parameters and lack of sufficient preparation on the existing SQL query. This enables attackers to append additional SQL queries into already existing queries, which can be used to extract sensitive information from the database. **Recommendations** For versions up to, and including, 4.0.1, update to a version higher than 4.0.1 to resolve the issue. As a temporary workaround, consider restricting access to the `id` parameter in the affected API endpoint until a patch is available.