Summary
A missing authorization check in phpMyFAQ's getIdFromSolutionId() method allows unauthenticated users to enumerate restricted FAQ entries by probing the /solution_id_{id}.html endpoint.
By iterating solution IDs, attackers can discover the existence and titles of FAQs intended only for specific users or groups, leaking sensitive metadata via redirect headers and canonical links.
Affected context
This vulnerability occurs in phpMyFAQ instances where:
- The application exposes the /solution_id_{id}.html endpoint publicly
- FAQ entries can be restricted to specific users or groups
- The getIdFromSolutionId() method is invoked without verifying the requester's permissions
In such deployments, restricted FAQ entries become partially discoverable to any unauthenticated visitor who can issue HTTP requests to the public frontend.
Exploit preconditions
- Attack surface: Public web interface of phpMyFAQ
- Required access: No authentication; any network-level access to the phpMyFAQ frontend is sufficient
- Trigger point: Requests to URLs of the form
/solution_id_{id}.html, where{id}is an integer or enumerated solution identifier - Why exploitation is possible: The getIdFromSolutionId() method resolves solution identifiers to FAQ records and returns information that reveals restricted entries without performing a permission check, allowing enumeration through sequential or automated ID probing
Why this happens
The root cause is a missing authorization control in the request handling flow that maps solution IDs to internal FAQ entries.
The getIdFromSolutionId() method is used to look up FAQ content based on a solution identifier, but it does not validate whether the current user is allowed to access the associated FAQ.
This behavior maps to CWE-863: Incorrect Authorization, where the system fails to perform an access control check for a sensitive resource, exposing metadata about restricted content through redirect Location headers and canonical links.
Potential impact
- Exposure of titles and identifiers of FAQs restricted to specific users or groups
- Inference of sensitive topics, projects, or internal initiatives based on FAQ metadata
- Leakage of security-related or operational information encapsulated in FAQ titles
- Facilitation of targeted social engineering by revealing internal terminology and structures
- Increased attack surface awareness for adversaries planning further intrusion attempts
General mitigation guidance
Mitigation typically focuses on ensuring that authorization checks are consistently enforced for all resource lookups, including indirect lookup endpoints:
- Apply uniform permission checks whenever resolving solution IDs or FAQ IDs, regardless of entry point
- Treat redirect responses and canonical links as sensitive, ensuring they only include information the requester is authorized to see
- Centralize access control logic so that all FAQ retrieval flows pass through the same permission enforcement mechanism
- Minimize exposure of internal identifiers and sensitive metadata in URLs, headers, and HTML metadata where possible
- Configure default roles and anonymous access so that restricted FAQs are invisible to unauthenticated users by design
How teams detect issues like this
Organizations can detect similar authorization issues through a combination of review and testing:
- Static analysis: Flag controller or routing code paths where data is returned or redirected based on identifiers without explicit permission checks
- Code review: Look for helper methods that retrieve sensitive resources (e.g., getIdFromSolutionId) and ensure they are always wrapped with consistent access control logic
- Security testing: Perform authenticated and unauthenticated probing of resource lookup endpoints, checking whether restricted content metadata appears in redirects, headers, or HTML metadata
- Logging and monitoring: Record access attempts to restricted solution IDs and detect unusual enumeration patterns (e.g., sequential ID requests from the same client)

