CVE-2025-56421
SQL Injection in LimeSurvey Pre-6.15.4 Exposes Sensitive Data
Publication date: 2026-03-10
Last updated on: 2026-03-20
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| limesurvey | limesurvey | to 6.15.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-56421 is a SQL Injection vulnerability found in LimeSurvey versions prior to 6.15.4+250710.
This vulnerability occurs due to improper input validation, which allows a remote attacker to inject specially crafted input directly into SQL queries.
By exploiting this flaw, an attacker can execute arbitrary SQL commands on the backend database.
This can lead to exposure of sensitive information such as user credentials, survey responses, and administrative data.
The issue is fixed by upgrading LimeSurvey to version 6.15.4+250710 or later.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive data stored in the LimeSurvey database.
- Exposure of user credentials which could lead to account compromise.
- Disclosure of survey responses, potentially revealing confidential or personal information.
- Access to administrative data that could allow further exploitation or control over the LimeSurvey installation.
Overall, it can lead to data breaches and loss of trust in the affected system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability is a SQL Injection flaw in LimeSurvey versions prior to 6.15.4+250710 caused by improper input validation. Detection typically involves testing for SQL injection points by sending specially crafted inputs to the LimeSurvey application and observing if unexpected database errors or sensitive data are returned.'}, {'type': 'paragraph', 'content': 'Common detection methods include using automated vulnerability scanners that support SQL injection detection or manual testing with tools like sqlmap.'}, {'type': 'list_item', 'content': 'Use sqlmap to test the LimeSurvey URL for SQL injection: sqlmap -u "http://target-limesurvey-url" --batch'}, {'type': 'list_item', 'content': "Manually test input fields by injecting typical SQL payloads such as ' OR '1'='1 or ' UNION SELECT NULL-- and observe the responses."}] [1]
What immediate steps should I take to mitigate this vulnerability?
The primary and immediate mitigation step is to upgrade LimeSurvey to version 6.15.4+250710 or later, where this SQL Injection vulnerability has been fixed.
Until the upgrade can be applied, consider restricting access to the LimeSurvey application to trusted networks or users to reduce exposure.
Additionally, review and harden input validation and sanitization mechanisms if possible, and monitor logs for suspicious activity indicating attempted exploitation.