{"answers":{"affected":"2 open source packages ship an affected version, including limesurvey/limesurvey. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-56421 in the wild and no public exploit code.","fix":"Upgrade limesurvey/limesurvey to 6.15.4 or later.","what":"CVE-2025-56421 is a high-severity SQL injection vulnerability in Limesurvey Limesurvey, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-56421 and fix it if it is affected.\n\nWhat it is: CVE-2025-56421 is a high-severity SQL injection vulnerability in Limesurvey Limesurvey, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-56421 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- limesurvey/limesurvey (Packagist): affected all versions; fixed in 6.15.4\n- limesurvey/limesurvey (Packagist): affected all versions; fixed in 6.15.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-56421/ (Markdown: https://insights.sbomify.com/CVE-2025-56421/index.md)","id":"CVE-2025-56421","markdown":"https://insights.sbomify.com/CVE-2025-56421/index.md","name":"CVE-2025-56421","record":{"aliases":["GHSA-rccq-2fxq-7x3h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LimeSurvey","requires_auth":"none","summary":"Remote attackers can exploit SQL injection in LimeSurvey to obtain sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"limesurvey","vendor":"limesurvey"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL Injection vulnerability in LimeSurvey before v.6.15.4+250710 allows a remote attacker to obtain sensitive information from the database.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"LimeSurvey is vulnerable to SQL injection","id":"CVE-2025-56421","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"limesurvey:limesurvey","products":["limesurvey:limesurvey"],"type":"sql_injection","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Deserialization in n/a","id":"CVE-2025-56422"},"packages":[{"ecosystem":"Packagist","fixed":["6.15.4"],"introduced":["0"],"last_affected":[],"package":"limesurvey/limesurvey","purl":null,"source":"GHSA-rccq-2fxq-7x3h"},{"ecosystem":"Packagist","fixed":["6.15.4"],"introduced":["0"],"last_affected":[],"package":"limesurvey/limesurvey","purl":"pkg:composer/limesurvey/limesurvey","source":"GHSA-rccq-2fxq-7x3h"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-56413"},"products":["n/a"],"published":"2026-03-10","related":[{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2025-56422","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-48008","kev_date_added":null,"published":"2023-01-27"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-25019","kev_date_added":null,"published":"2021-02-14"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-11455","kev_date_added":null,"published":"2020-04-01"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2019-16184","kev_date_added":null,"published":"2019-09-09"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2019-9960","kev_date_added":null,"published":"2019-03-24"},{"cvss_score":9.8,"headline":"TCPDF vulnerable to attackers triggering deserialization of arbitrary data","id":"CVE-2018-17057","kev_date_added":null,"published":"2018-09-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Remote attackers can exploit SQL injection in LimeSurvey to obtain sensitive database information.","url":"https://insights.sbomify.com/CVE-2025-56421/"}