# CVE-2025-41076: Multiple vulnerabilities in Limesurvey

> An attacker can trigger a 500 error via a malformed session cookie, exposing internal backend details like database structure and framework information.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** BIT-limesurvey-2025-41076, GHSA-3q6j-5f25-xfc9

## What is CVE-2025-41076?

CVE-2025-41076 is a medium-severity vulnerability in Limesurvey Limesurvey, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In version 6.13.0 of LimeSurvey, any external user can cause a 500 error in the survey system by sending a malformed session cookie. Instead of displaying a generic error message, the system exposes internal backend information, including the use of the Yii framework, the MySQL/MariaDB database engine, the table name 'lime_sessions', primary keys, and fragments of the content that caused the conflict. This information can simplify the collection of data about the internal architecture of the application by an attacker.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2025-41076?

1 open source package ship an affected version, including limesurvey. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `limesurvey` | Bitnami | From 6.13.0 | 6.15.5 |

Products: Limesurvey Limesurvey.

## How do I fix CVE-2025-41076?

Upgrade limesurvey to 6.15.5 or later.

## Is CVE-2025-41076 being exploited?

There is no known exploitation of CVE-2025-41076 in the wild and no public exploit code.

## Other vulnerabilities in Limesurvey Limesurvey

- [CVE-2025-56422](https://insights.sbomify.com/CVE-2025-56422/): Deserialization in n/a (critical 9.8)
- [CVE-2022-48008](https://insights.sbomify.com/CVE-2022-48008/): File upload in n/a (critical 9.8)
- [CVE-2019-25019](https://insights.sbomify.com/CVE-2019-25019/): SQL injection in n/a (critical 9.8)
- [CVE-2020-11455](https://insights.sbomify.com/CVE-2020-11455/): Path traversal in n/a (critical 9.8)
- [CVE-2019-16184](https://insights.sbomify.com/CVE-2019-16184/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41076 and fix it if it is affected.

What it is: CVE-2025-41076 is a medium-severity vulnerability in Limesurvey Limesurvey, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41076 in the wild and no public exploit code.

Affected packages and fixed versions:
- limesurvey (Bitnami): affected from 6.13.0; fixed in 6.15.5

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-41076/ (Markdown: https://insights.sbomify.com/CVE-2025-41076/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-41076
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-41076
- OSV: https://osv.dev/vulnerability/CVE-2025-41076

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-41076/
Summaries are generated and may contain mistakes; the official description above is the record.