Summary
Maccms v10 exposes the user-list API without effective authentication or authorization checks. An unauthenticated remote attacker may use crafted pagination parameters to retrieve sensitive information about registered users.
Affected context
The issue occurs in the /api.php/user/get_list endpoint of Maccms v10 deployments using the affected application version. Risk is present when the endpoint is reachable over a network and does not require a valid session or enforce authorization before returning user records.
Exploit preconditions
- Attack surface: Network-accessible HTTP API endpoint
- Required access: No authentication may be required
- Trigger point: A GET request to
/api.php/user/get_listwithlimitandoffsetparameters - Why exploitation is possible: The endpoint may return user data without first verifying identity, session validity, or permission to access the requested records
Why this happens
The underlying flaw is a missing access-control decision at a sensitive API boundary. The application exposes user records without consistently authenticating callers and checking whether they are authorized to retrieve the requested resource, which maps to CWE-284: Improper Access Control.
Potential impact
- Unauthorized parties may enumerate registered users
- Sensitive account information could be disclosed
- User privacy may be compromised
- Retrieved records could support targeted phishing or account attacks
- Excessive pagination requests may increase information exposure or application load
General mitigation guidance
Mitigation generally focuses on enforcing authentication and object- or function-level authorization before processing user-list requests.
Common defensive patterns include:
- Require authenticated sessions for administrative or user-directory APIs
- Apply explicit role and permission checks at the endpoint boundary
- Use deny-by-default access policies for sensitive data
- Return only the minimum fields required by an authorized use case
- Enforce bounded pagination, rate limits, and query-result limits
- Avoid exposing user directories to untrusted callers unless necessary
- Apply least privilege to service identities and administrative roles
How teams detect issues like this
Organizations can identify similar weaknesses through:
- Static and dynamic analysis of API routes for missing authentication or authorization middleware
- Code review checks for sensitive endpoints that query user records before access decisions
- API inventory reviews that classify data exposure and required permissions
- Integration tests that verify anonymous, low-privilege, and unauthorized requests receive denial responses
- Web application firewall or gateway policies requiring authentication for protected API paths
- Monitoring for repeated unauthenticated requests and broad pagination across user-list endpoints

