First published: Mon Mar 25 2024(Updated: )
### Summary The `email` field in phpMyFAQ's user control panel page is vulnerable to stored XSS attacks due to the inadequacy of PHP's `FILTER_VALIDATE_EMAIL` function, which only validates the email format, not its content. This vulnerability enables an attacker to execute arbitrary client-side JavaScript within the context of another user's phpMyFAQ session. ### Details Despite using PHP's `FILTER_VALIDATE_EMAIL` function, the email field does not adequately validate the content of the email address. This means that malicious input, such as JavaScript code, can be accepted and stored in the database without being detected. When the stored data is retrieved and displayed on web pages, it is not properly sanitized to remove or neutralize any potentially harmful content, such as JavaScript code which leads to Stored XSS. ### PoC 1. Login as any user, go to the user control panel, change email to any valid email and intercept the request. 2. Modify the request’s email parameter to the following payload: `"><svg/onload=confirm('XSS')>"@x.y`  3. Send the request and see that the XSS is triggered in the user control panel page.  4. Also affects any user who browse to "../admin/?action=user&user_action=listallusers"  ### Impact This allows an attacker to execute arbitrary client side JavaScript within the context of another user's phpMyFAQ session.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/phpmyfaq/phpmyfaq | =3.2.5 | 3.2.6 |
phpMyFAQ | =3.2.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-27300 is classified as a moderate severity vulnerability due to its potential for stored XSS attacks.
To fix CVE-2024-27300, upgrade phpMyFAQ to version 3.2.6 or later.
CVE-2024-27300 allows attackers to execute arbitrary JavaScript in the context of the user's session.
CVE-2024-27300 affects phpMyFAQ version 3.2.5 and earlier.
Currently, there are no effective workarounds for CVE-2024-27300 aside from upgrading to a secure version.