CVE-2024-27300: phpmyfaq/phpmyfaq - Stored Cross-site Scripting at user email

phpmyfaq/phpmyfaq Updated 02 Oct 2025

Summary

25/03/2024
Yes i
Moderate
5.5

CVE-2024-27300: phpMyFAQ stored Cross-site Scripting at user email. Affects phpmyfaq/phpmyfaq versions >= 3.2.5, < 3.2.6. Fixed in 3.2.6. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

phpmyfaq/phpmyfaq is an open-source FAQ management system written in PHP. It provides a user-friendly interface for creating and managing frequently asked questions. The system allows users to register accounts and update their personal information, including their email address. However, a vulnerability in the email field validation process allows for the storage of malicious JavaScript code, leading to a stored cross-site scripting (XSS) attack.

Vulnerability Detail

The vulnerability arises from the inadequate validation of the email field in phpMyFAQ's user control panel page. While PHP's FILTER_VALIDATE_EMAIL function is used to validate the email format, it fails to validate the content of the email address. This allows an attacker to input and store JavaScript code in the database without detection. When the stored data is later retrieved and displayed on web pages, the lack of proper sanitization exposes users to potential XSS attacks. An attacker can execute arbitrary client-side JavaScript within the context of another user's phpMyFAQ session, potentially leading to unauthorized actions or data theft.

How To Fix

Minimum fixed version

3.2.6

This is the first release that contains the fix.

composer require phpmyfaq/phpmyfaq:3.2.6

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, administrators can manually inspect and sanitize the email field entries in the database to remove any potentially malicious content. Regularly monitoring and reviewing user accounts for suspicious activity can also help mitigate the risk of exploitation.

Conclusion

The stored cross-site scripting vulnerability in phpmyfaq/phpmyfaq's user email field poses a moderate risk to the security and integrity of the application. It allows an attacker to execute arbitrary client-side JavaScript within the context of another user's session, potentially leading to unauthorized actions or data theft. It is crucial to promptly update to version 3.2.6 or later to mitigate this vulnerability. Regular monitoring of user accounts and implementing proper input validation and sanitization practices can further enhance the security of the application.

See every vulnerability recorded for phpmyfaq/phpmyfaq →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary client-side JavaScript within the context of another user's phpMyFAQ session. This can lead to unauthorized actions, data theft, or the manipulation of user interactions within the application.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your composer.lock file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

Yes, a fix has been released in version 3.2.6 of phpmyfaq/phpmyfaq. It is recommended to update to this version or later to mitigate the vulnerability.

As mentioned earlier, a temporary workaround involves manually inspecting and sanitizing the email field entries in the database. Additionally, regularly monitoring user accounts for suspicious activity can help detect and mitigate potential exploitation.

No, this vulnerability requires an authenticated user to exploit it. However, if an attacker gains access to a valid user account, they can execute the XSS attack within the context of that user's session.

Related vulnerabilities

Recent vulnerabilities recorded for phpmyfaq/phpmyfaq.

How To Fix

Minimum fixed version

3.2.6

This is the first release that contains the fix.

composer require phpmyfaq/phpmyfaq:3.2.6

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback