# CVE-2026-8208: Code injection in gibbon

> Attackers with Teacher privileges can achieve remote code execution by manipulating report archive settings to force PHP interpretation of uploaded zip files.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-px5v-8vpf-hw32

## What is CVE-2026-8208?

CVE-2026-8208 is a high-severity code injection vulnerability in gibbonedu gibbon, published on 9 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Gibbon versions before v30.0.01 are affected by a local file inclusion vulnerability resulting in RCE by changing the report archive directory and forcing interpretation of a user provided .zip as PHP. Successful exploitation requires Teacher or higher privileges. Exploitation could result in compromise of the underlying web server.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2026-8208?


## How do I fix CVE-2026-8208?

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

## Is CVE-2026-8208 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8208 and fix it if it is affected.

What it is: CVE-2026-8208 is a high-severity code injection vulnerability in gibbonedu gibbon, published on 9 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8208 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-2026-8208/ (Markdown: https://insights.sbomify.com/CVE-2026-8208/index.md)
```

## Sources

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

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