Unauthenticated database manipulation via unsanitized token parameter
Published Aug 1, 2025 · Updated Sep 11, 2025
SQL injection in LimeSurvey 2.65.1+170522 allows remote attackers to read, create, update, and delete database records via a token parameter. The /index.php endpoint incorporates the token parameter into an SQL operation without sufficient neutralization; public sources do not identify the responsible function or query. No authentication or user interaction is required, and successful requests can compromise database confidentiality, integrity, and availability.
Summary
What happened
SQL injection in LimeSurvey 2.65.1+170522 allows remote attackers to read, create, update, and delete database records via a token parameter. The /index.php endpoint incorporates the token parameter into an SQL operation without sufficient neutralization; public sources do not identify the responsible function or query. No authentication or user interaction is required, and successful requests can compromise database confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-41375
- Published
- Aug 1, 2025
- Updated
- Sep 11, 2025
- Vendor
- LimeSurvey GmbH
- Product
- LimeSurvey
- Classifications
- CWE-89, CAPEC-66, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2025CVE publishedPublication date reported by the CVE source.
- Sep 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo