Summary
Admidio before version 5.0.12 contains a blind SQL injection vulnerability in the relation_type_list parameter processed by lists_show.php.
An unauthenticated attacker may manipulate database queries, bypass authentication conditions, and retrieve sensitive information such as password hashes and user credentials.
Affected context
The vulnerability occurs in Admidio installations that expose the affected list functionality and process attacker-controlled values in relation_type_list without safely separating data from SQL query logic. Exploitation may be possible without a valid account when the request reaches the vulnerable endpoint and the application accepts the relevant role and relation parameters.
Exploit preconditions
- Attack surface: Web-accessible
lists_show.phpfunctionality - Required access: Typically no authentication, if the endpoint is reachable and accepts the relevant request parameters
- Trigger point: Processing of the
relation_type_listparameter during list generation - Why exploitation is possible: User-controlled input is incorporated into database query processing without sufficient parameterization or equivalent query isolation
Why this happens
The underlying bug is SQL injection, mapped to CWE-89. The application treats externally supplied parameter content as part of SQL query structure rather than strictly as a data value.
When query construction does not consistently use parameterized statements, trusted query builders, or equivalent safeguards, attacker-controlled input may alter query behavior. Blind SQL injection can expose information indirectly through differences in responses, timing, or application behavior, even when database errors are not displayed.
Potential impact
- An attacker may bypass authentication-related checks
- Database contents could be disclosed
- Password hashes and user credentials may be exposed
- Application data could be modified or deleted
- Database availability could be disrupted
- Further compromise may be possible if database privileges are excessive
General mitigation guidance
Mitigation generally focuses on eliminating the flow of untrusted input into SQL syntax.
Common defensive patterns include:
- Use parameterized queries or safe query-builder interfaces for all database access
- Treat request parameters as untrusted regardless of whether an endpoint is publicly accessible
- Apply allowlisted validation for identifiers and enumerated relation types
- Keep authentication and authorization checks independent from user-controlled query criteria
- Use database accounts with only the permissions required by the application
- Avoid exposing detailed database errors or behavior that unnecessarily reveals query outcomes
- Add regression tests covering boundary values, invalid types, and unexpected parameter structures
How teams detect issues like this
Organizations can look for SQL injection risks through:
- Static analysis rules identifying string concatenation or interpolation in SQL construction
- Code review checks for request parameters passed directly to database APIs
- Tests that verify parameterized query usage and strict input validation
- Web application monitoring for anomalous values in
relation_type_listand related parameters - Database audit logs showing unusual query patterns, repeated conditional requests, or unexpected access to credential-related tables
- Policy enforcement requiring approved database-access abstractions and security testing before deployment
Automated code-review and application-security tools may help identify common query-construction patterns, but should be supplemented with manual review.

