Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-98gw-w575-h2ph | phpMyFAQ is Vulnerable to Stored XSS via Unsanitized Email Field in Admin FAQ Editor |
Tue, 07 Apr 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Phpmyfaq
Phpmyfaq phpmyfaq |
|
| CPEs | cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Phpmyfaq
Phpmyfaq phpmyfaq |
|
| Metrics |
cvssV3_1
|
Thu, 02 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Thorsten
Thorsten phpmyfaq |
|
| Vendors & Products |
Thorsten
Thorsten phpmyfaq |
Thu, 02 Apr 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | phpMyFAQ is an open source FAQ web application. Prior to version 4.1.1, an unauthenticated attacker can submit a guest FAQ with an email address that is syntactically valid per RFC 5321 (quoted local part) yet contains raw HTML — for example "<script>alert(1)</script>"@evil.com. PHP's FILTER_VALIDATE_EMAIL accepts this email as valid. The email is stored in the database without HTML sanitization and later rendered in the admin FAQ editor template using Twig's |raw filter, which bypasses auto-escaping entirely. This issue has been patched in version 4.1.1. | |
| Title | phpMyFAQ: Stored XSS via Unsanitized Email Field in Admin FAQ Editor | |
| Weaknesses | CWE-20 CWE-79 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-02T16:23:06.203Z
Reserved: 2026-03-12T15:29:36.558Z
Link: CVE-2026-32629
No data.
Status : Analyzed
Published: 2026-04-02T15:16:38.017
Modified: 2026-04-07T16:10:02.627
Link: CVE-2026-32629
No data.
OpenCVE Enrichment
Updated: 2026-04-08T19:56:18Z
Github GHSA