CVE-2025-56422
Deserialization Vulnerability in LimeSurvey Enables Remote Code Execution
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.14.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-56422 is a remote code execution vulnerability in LimeSurvey caused by unsafe deserialization of user-controlled input.
Specifically, LimeSurvey versions prior to 6.15.0+250623 improperly handle the deserialization process, allowing an attacker to supply a specially crafted serialized object.
This malicious input can trigger arbitrary code execution within the application context on the server.
The vulnerability is exploitable remotely.
How can this vulnerability impact me? :
This vulnerability allows a remote attacker to execute arbitrary code on the server running LimeSurvey.
Successful exploitation could lead to full compromise of the server, including unauthorized access, data theft, data manipulation, or disruption of services.
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?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2025-56422 vulnerability, you should upgrade LimeSurvey to version 6.15.0+250623 or later.
This update addresses the unsafe deserialization issue that allows remote code execution by properly handling user-controlled input.
Further details and updates can be found on the official LimeSurvey website and the LimeSurvey GitHub repository issue #4329.