Unauthorized comments via missing inactive-record check
Published Apr 5, 2023 · Updated Feb 10, 2025
Improper access control in phpMyFAQ before 3.1.12 allows remote authenticated users to post comments on inactive FAQ or news records. The ajaxservice.php comment-save path checks whether comments are enabled but does not reject a target record whose active flag is disabled. A registered account and an inactive record with comments enabled are required; exploitation writes a comment to content intended to remain unpublished.
Summary
What happened
Improper access control in phpMyFAQ before 3.1.12 allows remote authenticated users to post comments on inactive FAQ or news records. The ajaxservice.php comment-save path checks whether comments are enabled but does not reject a target record whose active flag is disabled. A registered account and an inactive record with comments enabled are required; exploitation writes a comment to content intended to remain unpublished.
The record
- CVE
- CVE-2023-1883
- Published
- Apr 5, 2023
- Updated
- Feb 10, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2023CVE publishedPublication date reported by the CVE source.
- Feb 10, 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.
Public exploit references
- Huntr inactive-record comment proof of conceptproof 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