CVE-2025-41074
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 · uneditedVulnerability in LimeSurvey 6.13.0 in the endpoint /optout that causes infinite HTTP redirects when accessed directly. This behavior can be exploited to generate a Denegation of Service (DoS attack), by exhausting server or client resources. The system is unable to break the redirect loop, which can cause service degradation or browser instability.
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 · moderate confidenceLimeSurvey 6.13.0 contains an infinite redirect vulnerability in the /optout endpoint. When accessed directly, the endpoint causes an endless loop of HTTP redirects, which can be exploited to exhaust server resources or cause browser instability, resulting in denial of service.
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= 6.13.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm LimeSurvey installationLook for LimeSurvey files in your web root directory, or check your web server configuration for LimeSurvey virtual hosts or aliases.Affected if LimeSurvey is not installed on this server, so the CVE does not apply.
-
Identify installed LimeSurvey versionCheck the version file (typically application/config/version.php or the admin interface under 'Configuration > Global settings > About'), or query the database version table if you have database access.Affected if The installed version is exactly 6.13.0; other versions are not affected by this specific CVE.
-
Locate the /optout endpointAccess your LimeSurvey base URL and navigate to the optout path (e.g., https://yourserver/index.php/optout or /optout), or inspect your web server routing configuration to confirm the route exists.Affected if The /optout endpoint does not exist or is not accessible, so the vulnerability cannot be triggered.
-
Test for infinite redirect behaviorUsing a browser or HTTP client (curl -I or similar), make a GET request to the /optout endpoint and observe the HTTP response headers. A vulnerable instance will return multiple 301/302 redirects in succession without reaching a final destination.Affected if The response shows a redirect loop (multiple 30x status codes without termination) when accessing /optout, indicating the vulnerability is present.
You are affected if LimeSurvey version 6.13.0 is installed and the /optout endpoint exhibits an infinite redirect loop when accessed.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper redirect logic in the /optout endpoint to break the redirect loop, likely by adding a terminal condition or correcting the redirect destination handling.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-41074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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