dbcve.org
LimesurveyApplication

CVE-2025-41376

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-01
Fix available
A fix is available. Upgrade to 3.0.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
CRLF Injection vulnerability in Limesurvey v2.65.1+170522.  This vulnerability could allow a remote attacker to inject arbitrary HTTP headers and perform HTTP response splitting attacks via '/index.php/survey/index/sid/<SID>/token/fwyfw%0d%0aCookie:%20POC'.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Limesurvey v2.65.1+170522 contains a CRLF injection vulnerability in the survey token handling functionality. Attackers can inject %0d%0a (carriage return/line feed) sequences via the token parameter to inject arbitrary HTTP headers and perform HTTP response splitting attacks.

MitigationImplement strict input validation to reject or properly encode CRLF sequences in the token parameter before any use in HTTP responses. Sanitize all user-supplied input in the survey endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LimesurveyApplication
Affected:>= 2.65.1, < 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Limesurvey version
    Locate the version information in the application (typically in admin panel, about page, or version file) and compare it against the affected range: >= 2.65.1 and < 3.0.0
    Affected if The installed version is 2.65.1 or higher but lower than 3.0.0
  2. Confirm survey functionality is active
    Verify that the LimeSurvey survey creation and submission features are enabled and accessible in the installation
    Affected if Survey functionality is enabled and publicly or internally accessible
  3. Identify token parameter exposure
    Check if survey URLs accept a token parameter (commonly seen in survey invitation links ending with ?token=xxxxx)
    Affected if The survey token parameter is accepted and reflected in HTTP responses without filtering CRLF sequences

You are affected if running Limesurvey version 2.65.1 or higher but below 3.0.0 with the survey token feature enabled and the token parameter reflected in responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 3.0.0 or later
Fixed in 3.0.0
Interim mitigation

Implement strict input validation to reject or properly encode CRLF sequences in the token parameter before any use in HTTP responses. Sanitize all user-supplied input in the survey endpoint.

Fix this in Limesurvey Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41376 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data