Authenticated script injection via unsanitized comments
Published Mar 31, 2023 · Updated Feb 11, 2025
Cross-site scripting in phpMyFAQ before 3.1.12 allows remote authenticated users to inject script through comment fields. The ajaxservice comment path stored nl2br-transformed text without stripping tags, while Comments rendered usernames without HTML encoding. A low-privileged account can place script in comment output, enabling browser-context data access or actions when the affected content is rendered.
Summary
What happened
Cross-site scripting in phpMyFAQ before 3.1.12 allows remote authenticated users to inject script through comment fields. The ajaxservice comment path stored nl2br-transformed text without stripping tags, while Comments rendered usernames without HTML encoding. A low-privileged account can place script in comment output, enabling browser-context data access or actions when the affected content is rendered.
The record
- CVE
- CVE-2023-1761
- Published
- Mar 31, 2023
- Updated
- Feb 11, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 31, 2023CVE publishedPublication date reported by the CVE source.
- Feb 11, 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.12
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
No public exploit references are available in this record.
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