Admidio: Second-Order SQL Injection via List Configuration (lsc_special_field, lsc_sort, lsc_filter)
admidio
admidio
| Product | Affected | Fixed in |
|---|---|---|
| admidio/admidio Packagist |
|
|
Admidio is an open-source user management solution. Versions 5.0.6 and below are vulnerable to arbitrary SQL Injection through the MyList configuration feature. The MyList configuration feature lets authenticated users define custom list column layouts, storing user-supplied column names, sort directions, and filter conditions in the adm_list_columns table via prepared statements. However, these stored values are later read back and interpolated directly into dynamically constructed SQL queries without sanitization or parameterization, creating a classic second-order SQL injection vulnerability (safe write, unsafe read). An attacker can exploit this to inject arbitrary SQL, potentially reading, modifying, or deleting any data in the database and achieving full database compromise. This issue has been fixed in version 5.0.7.
From the CVE record · GitHub_M
Admidio versions below 5.0.7 are vulnerable to second-order SQL injection in MyList configuration: stored user-supplied values are later inserted into SQL queries without sanitization or parameterization. An authenticated attacker can inject SQL that may read, modify, or delete database data.
Teams running admidio/admidio versions below 5.0.7 should check their installations.