CVE-2025-56421 json
LimeSurvey is vulnerable to SQL injection
published 8mo ago modified 4mo ago also GHSA-rccq-2fxq-7x3h , EUVD-2025-208502
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
SQL Injection vulnerability in LimeSurvey before v.6.15.4+250710 allows a remote attacker to obtain sensitive information from the database.
Patch / fix
- packagist limesurvey/limesurvey 6.15.4
- github.com/LimeSurvey/LimeSurvey@d6c3c78 commit
- github.com/LimeSurvey/LimeSurvey#4328 pull request
Is CVE-2025-56421 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | limesurvey/limesurvey | <6.15.4 |
6.15.4 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/LimeSurvey/LimeSurvey/pull/4328
web
-
github.com
/LimeSurvey/LimeSurvey/commit/d6c3c780cdd17d5eef1c8c69ad0105beffa2374f
web
-
github.com
/hongancalif/security-advisories/blob/main/CVE-2025-56421.md
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-56421
advisory
-
github.com
/LimeSurvey/LimeSurvey
package
-
limesurvey.com
web
Sources
- CVE List CVE-2025-56421
- GitHub Advisory GHSA-rccq-2fxq-7x3h
- NVD CVE-2025-56421
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.