# CVE-2025-26211: Gibbon before 29.0.00 allows CSRF.


- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 May 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-5vqp-77qj-7r83

## What is CVE-2025-26211?

CVE-2025-26211 is a low-severity vulnerability in GibbonEdu Gibbon, published on 27 May 2025. 

### Official description

Gibbon before 29.0.00 allows CSRF.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Gibbonedu Gibbon.

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

No fix has been published for CVE-2025-26211 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-26211 being exploited?

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

## Other vulnerabilities in GibbonEdu Gibbon

- [CVE-2024-24724](https://insights.sbomify.com/CVE-2024-24724/): Code injection in n/a (critical 9.8)
- [CVE-2023-45878](https://insights.sbomify.com/CVE-2023-45878/): File upload in n/a (critical 9.8)
- [CVE-2023-34598](https://insights.sbomify.com/CVE-2023-34598/): Path traversal in n/a (critical 9.8)
- [CVE-2024-24725](https://insights.sbomify.com/CVE-2024-24725/): Deserialization in n/a (high 8.8)
- [CVE-2022-27305](https://insights.sbomify.com/CVE-2022-27305/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26211 is a low-severity vulnerability in GibbonEdu Gibbon, published on 27 May 2025. 
Exploitation: There is no known exploitation of CVE-2025-26211 in the wild and no public exploit code.

Affected product: GibbonEdu Gibbon. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-26211/ (Markdown: https://insights.sbomify.com/CVE-2025-26211/index.md)
```

## Sources

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

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