# CVE-2024-56199: phpMyFAQ Vulnerable to Stored HTML Injection at FAQ > Attackers can inject malicious HTML into phpMyFAQ, causing denial of service and potential phishing or defacement attacks. - **Severity:** Medium 5.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 2 Jan 2025 - **Updated:** 2 Jan 2025 - **Also known as:** GHSA-ww33-jppq-qfrp ## What is CVE-2024-56199? CVE-2024-56199 is a medium-severity cross-site scripting vulnerability in Phpmyfaq Phpmyfaq, published on 2 Jan 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description phpMyFAQ is an open source FAQ web application. Starting no later than version 3.2.10 and prior to version 4.0.2, an attacker can inject malicious HTML content into the FAQ editor at `http[:]//localhost/admin/index[.]php?action=editentry`, resulting in a complete disruption of the FAQ page's user interface. By injecting malformed HTML elements styled to cover the entire screen, an attacker can render the page unusable. This injection manipulates the page structure by introducing overlapping buttons, images, and iframes, breaking the intended layout and functionality. Exploiting this issue can lead to Denial of Service for legitimate users, damage to the user experience, and potential abuse in phishing or defacement attacks. Version 4.0.2 contains a patch for the vulnerability. Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-56199? 4 open source packages ship an affected version, including phpmyfaq/phpmyfaq and thorsten/phpmyfaq. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `phpmyfaq/phpmyfaq` | Packagist | From 3.2.10 to 4.0.1 | None | | `phpmyfaq/phpmyfaq` | Packagist | From 3.2.10 to 4.0.1 | None | | `thorsten/phpmyfaq` | Packagist | From 3.2.10 to 4.0.1 | None | | `thorsten/phpmyfaq` | Packagist | From 3.2.10 to 4.0.1 | None | Products: Phpmyfaq Phpmyfaq. ## How do I fix CVE-2024-56199? No fix has been published for CVE-2024-56199 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-56199 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56199 exists. ## Other vulnerabilities in Phpmyfaq Phpmyfaq - [CVE-2023-0310](https://insights.sbomify.com/CVE-2023-0310/): Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq (critical 9.8) - [CVE-2022-4407](https://insights.sbomify.com/CVE-2022-4407/): Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq (critical 9.8) - [CVE-2017-11187](https://insights.sbomify.com/CVE-2017-11187/): Security feature bypass in n/a (critical 9.8) - [CVE-2026-76213](https://insights.sbomify.com/CVE-2026-76213/): phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle (critical 9.1) - [CVE-2026-76214](https://insights.sbomify.com/CVE-2026-76214/): phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-56199 and fix it if it is affected. What it is: CVE-2024-56199 is a medium-severity cross-site scripting vulnerability in Phpmyfaq Phpmyfaq, published on 2 Jan 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56199 exists. Affected packages and fixed versions: - phpmyfaq/phpmyfaq (Packagist): affected from 3.2.10 up to 4.0.1; no fix listed - phpmyfaq/phpmyfaq (Packagist): affected from 3.2.10 up to 4.0.1; no fix listed - thorsten/phpmyfaq (Packagist): affected from 3.2.10 up to 4.0.1; no fix listed - thorsten/phpmyfaq (Packagist): affected from 3.2.10 up to 4.0.1; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-56199/ (Markdown: https://insights.sbomify.com/CVE-2024-56199/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56199 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56199 - OSV: https://osv.dev/vulnerability/CVE-2024-56199 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-56199/ Summaries are generated and may contain mistakes; the official description above is the record.