Miggo Logo

CVE-2024-56199:
phpMyFAQ Vulnerable to Stored HTML Injection at FAQ

5.2

CVSS Score
3.1

Basic Information

EPSS Score
0.3%
Published
1/2/2025
Updated
1/2/2025
KEV Status
No
Technology
TechnologyPHP

Technical Details

CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:L
Package NameEcosystemVulnerable VersionsFirst Patched Version
phpmyfaq/phpmyfaqcomposer>= 3.2.10, <= 4.0.1
thorsten/phpmyfaqcomposer>= 3.2.10, <= 4.0.1

Vulnerability Intelligence
Miggo AIMiggo AI

Miggo AIRoot Cause Analysis

The vulnerability stems from two key failures:

  1. Input Handling: The FAQ entry submission endpoint (admin/index.php?action=editentry) lacks server-side HTML sanitization when persisting user content. This allows attackers to store malicious payloads.
  2. Output Rendering: The FAQ display layer directly renders stored content without proper escaping. The PoC demonstrates successful DOM manipulation through unescaped style attributes and HTML elements, confirming insufficient output encoding. While exact function names/paths aren't provided in disclosures, the pattern matches common PHP CMS architectures where admin controllers handle content storage and view templates handle rendering. The high confidence in rendering functions stems from the PoC's visual impact requiring successful DOM injection.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

WAF Protection Rules

WAF Rule

### Summ*ry *u* to insu**i*i*nt v*li**tion on t** *ont*nt o* n*w **Q posts, it is possi*l* *or *ut**nti**t** us*rs to inj**t m*li*ious *TML or J*v*S*ript *o** t**t **n imp**t ot**r us*rs vi*win* t** **Q. T*is vuln*r**ility *ris*s w**n us*r-provi*** i

Reasoning

T** vuln*r**ility st*ms *rom two k*y **ilur*s: *. Input **n*lin*: T** **Q *ntry su*mission *n*point (**min/in**x.p*p?**tion=**it*ntry) l**ks s*rv*r-si** *TML s*nitiz*tion w**n p*rsistin* us*r *ont*nt. T*is *llows *tt**k*rs to stor* m*li*ious p*ylo**s