Sign in
Deutsch English Español Polski
Medium

phpMyFAQ Stored HTML Injection at contentLink

  • Disclosed: 25.03.2024
  • Updated: 11.10.2026 10:22

Summary

Due to insufficient validation on the contentLink parameter, it is possible for unauthenticated users to inject HTML code to the page which might affect other users. Also, requires that adding new FAQs is allowed for guests and that the admin doesn't check the content of a newly added FAQ.

PoC

  1. Browse to ../phpmyfaq/index.php?action=add&cat=0 , enter https://test.com?p=<h1>HTML_INJECTION</h1> for the contentLink parameter. image

  2. Verify the HTML injection by viewing the FAQ itself, “All categories” → “CategoryName” → ”QuestionName”. image

Impact

Attackers can manipulate the appearance and functionality of web pages by injecting malicious HTML code. This can lead to various undesirable outcomes, such as defacing the website, redirecting users to malicious sites, or altering the content to deceive users. Additionally, unauthenticated HTML injection can compromise user privacy by displaying sensitive information or misleading content. It undermines the integrity of the application and erodes user trust, potentially resulting in loss of reputation and credibility.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package phpmyfaq/phpmyfaq >= 3.2.5, < 3.2.6 3.2.6

References

CVSS score 5.1/10
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weakness (CWE)
CWE-79, CWE-80
Platform
Composer
Package
phpmyfaq/phpmyfaq
Disclosed
25.03.2024
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-48vw-jpf8-hwqh - CC BY 4.0

Vulnerability history: phpmyfaq/phpmyfaq

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (47) in the archive
Total entries
47
First → latest
10.2022 09.2026
Without a fix
2
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 18
  • Medium 25
  • Low 2

Disclosures per year

Severity:
  1. phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion
    High CVE-2026-56738 < 4.1.6 4.1.6
  2. phpMyFAQ's two-factor authentication login bypasses the password factor
    High · 8.1 CVE-2026-56737 >= 3.2.0, < 4.1.6 4.1.6
  3. phpMyFAQ has Stored XSS in Admin FAQ Editor via HTML Entity Bypass in Frontend FAQ Submission
    High · 8.2 CVE-2026-56736 < 4.2.0-alpha 4.2.0-alpha
  4. phpMyFAQ privilege escalation: GroupController::updatePermissions lets a GROUP_EDIT admin grant rights they do not hold
    High · 8.8 CVE-2026-57995 < 4.1.5 4.1.5
  5. phpMyFAQ has an incomplete fix for GHSA-xvp4-phqj-cjr3 — editUser() and updateUserRights() lack authorization guards
    High · 8.1 CVE-2026-56396 < 4.1.4 4.1.4
  6. phpMyFAQ: Missing Password Reset Token Allows Account Takeover via Username/Email Enumeration
    High · 8.2 CVE-2026-35675 < 4.1.3 4.1.3
  7. phpMyFAQ: Default Empty API Token Authentication Bypass
    High · 7.5 CVE-2026-35672 < 4.1.3 4.1.3
  8. phpMyFAQ: IDOR Account Takeover
    High · 8.8 CVE-2026-35671 < 4.1.3 4.1.3
  9. phpMyFAQ: Unauthenticated Password Reset Endpoint Allows User Enumeration and Forced Password Change Without Token Validation
    High · 8.2 CVE-2026-35676 < 4.1.3 4.1.3
  10. phpMyFAQ has unauthenticated SQL injection via User-Agent header in BuiltinCaptcha
    Critical · 9.8 CVE-2026-46364 < 4.1.2 4.1.2
  11. phpMyFAQ has unauthenticated FAQ permission bypass via getFaqBySolutionId fallback query
    High · 7.5 CVE-2026-46366 < 4.1.2 4.1.2
  12. phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields
    High · 7.5 CVE-2026-46359 < 4.1.2 4.1.2
  13. phpMyFAQ enables unauthenticated 2FA brute-force attack via /admin/check acceptance of arbitrary user-id
    Critical · 9.1 CVE-2026-45010 < 4.1.2 4.1.2
  14. phpMyFAQ has stored XSS via Utils::parseUrl() in comment rendering
    High · 7.6 CVE-2026-46367 >= 4.1.1, < 4.1.2 4.1.2
  15. phpMyFAQ: Path Traversal - Arbitrary File Deletion in MediaBrowserController
    High · 8.7 CVE-2026-34728 < 4.1.1 4.1.1
  16. phpMyFAQ has Authenticated SQL Injection in Configuration Update Functionality
    High · 7.2 CVE-2025-62519 < 4.0.14 4.0.14
  17. phpMyFAQ's File Upload Bypass at Category Image Leads to RCE
    High · 7.2 CVE-2024-28105 >= 3.2.5, < 3.2.6 3.2.6
  18. phpMyFAQ SQL injections at insertentry & saveentry
    High · 8.8 CVE-2024-28107 >= 3.2.5, < 3.2.6 3.2.6
  19. phpMyFAQ Stored HTML Injection at contentLink this entry
    Medium · 5.1 CVE-2024-28108 >= 3.2.5, < 3.2.6 3.2.6
  20. phpMyFAQ SQL Injection at "Save News"
    High · 8.8 CVE-2024-27299 >= 3.2.5, < 3.2.6 3.2.6
  21. phpMyFAQ vulnerable to Cross-site Scripting
    High · 8.4 CVE-2022-3608 < 3.2.0-alpha 3.2.0-alpha

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Privacy policy

Free to subscribe. Unsubscribe with one click in any email.