CVE 8.8 HIGH

LimeSurvey RemoteControl invite_participants/remind_participants SQL Injection_CVE-2026-50636

8.8 / 10
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Description

The RemoteControl API methods invite_participants and remind_participants pass a caller-supplied token-ID array into TokenDynamic::findUninvited(), which concatenates the values directly into a tid IN ('...') SQL clause without parameterization or input validation. A remote, authenticated attacker holding the tokens/update permission on a survey can inject a crafted array element to perform SQL injection. Because LimeSurvey configures its PDO connection with emulated prepared statements (emulatePrepare = true) and does not disable MySQL multi-statements, the injection supports stacked queries: the attacker can append arbitrary additional statements (INSERT/UPDATE/DELETE/DROP/CREATE) after the original SELECT. This permits both arbitrary read of any data in the database, such as administrator bcrypt password hashes (lime_users), survey response PII, session records, and global settings, all recoverable via a SLEEP() time-based blind oracle, and arbitrary write/destruction of that data, including directly overwriting the administrator password hash for immediate account takeover or dropping/truncating tables. Reads and writes extend to any schema the application's database user can access. The RemoteControl interface (RPCInterface = json/xml) must be enabled, which is not the default.

AI Analysis

SQL injection vulnerability in LimeSurvey RemoteControl API methods invite_participants and remind_participants, allowing arbitrary read and write access to the database.

Basic Information

ID CVE-2026-50636
Source VulnCheck
Published Jun 9, 2026 at 17:34

Affected Product

Vendor LimeSurvey
Product LimeSurvey
Affected Versions LimeSurvey LimeSurvey 0

CWE Classification

AI Assessment

AI Score 8.8 / 10
AI Severity High
Vendor LimeSurvey
Product LimeSurvey

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.