Authenticated code injection via unsanitized question markup
Published Feb 12, 2023 · Updated Mar 21, 2025
Code injection in phpMyFAQ before 3.1.11 allows remote authenticated users to inject executable markup through submitted questions. The ajaxservice.php question handler accepts the POST question value with FILTER_UNSAFE_RAW and stores it without stripping HTML tags. Low-privileged access to the question-submission path is sufficient; injected browser code can read or alter data available to a viewer, but no service interruption is reported.
Summary
What happened
Code injection in phpMyFAQ before 3.1.11 allows remote authenticated users to inject executable markup through submitted questions. The ajaxservice.php question handler accepts the POST question value with FILTER_UNSAFE_RAW and stores it without stripping HTML tags. Low-privileged access to the question-submission path is sufficient; injected browser code can read or alter data available to a viewer, but no service interruption is reported.
The record
- CVE
- CVE-2023-0788
- Published
- Feb 12, 2023
- Updated
- Mar 21, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-94, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2023CVE publishedPublication date reported by the CVE source.
- Mar 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.1.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr proof of concept for submitted-question code injectionproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo