/

CVE-2026-82655

Severity:

HIGH RISK

(7.5)

Blind SQL Injection (CWE-89) in Admidio lists_show.php

CVE-2026-82655

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Unauthorized Database Access and Authentication Bypass

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

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.php functionality
  • Required access: Typically no authentication, if the endpoint is reachable and accepts the relevant request parameters
  • Trigger point: Processing of the relation_type_list parameter 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_list and 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.

Sources

SourceLink
github.comgithub.com/Admidio/admidio/security/advisories/GHSA-p5cp-mhvx-w392
vulncheck.comvulncheck.com/advisories/admidio-before-5.0.12-sql-injection-via-relation-type-list

Frequently asked

questions

Yes, exploitation may be possible remotely when the affected lists_show.php functionality is reachable over the web and accepts the vulnerable parameters.

The described issue allows unauthenticated attackers to target the endpoint, although deployment-specific access controls may affect reachability.

Ensure that all database operations use parameterized queries or an equivalent safe abstraction, while validating request values against strict allowlists.

Combine secure database APIs, least-privilege database accounts, focused code review, automated scanning, regression tests, and monitoring for anomalous query behavior.

Find out what's already
exploitable in your codebase.