# CVE-2026-116895: REDAXO before 5.21.5 CSRF via Safe Mode Toggle Parameter


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-423v-8x3h-gxr3, GHSA-qx28-m2wr-99m4

## What is CVE-2026-116895?

CVE-2026-116895 is a medium-severity vulnerability in redaxo core, published on 27 Oct 2026. 

### Official description

REDAXO before 5.21.5 contains a cross-site request forgery vulnerability because the backend processes the safemode GET parameter in index.php without validating a CSRF token. Attackers can lure a logged-in administrator into opening a crafted link to disable global safe mode, writing safe_mode: false to config.yml, or enable session safe mode, disabling backend addons.

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

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


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

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

## Is CVE-2026-116895 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116895 is a medium-severity vulnerability in redaxo core, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116895 in the wild and no public exploit code.

Affected product: redaxo core. 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-116895/ (Markdown: https://insights.sbomify.com/CVE-2026-116895/index.md)
```

## Sources

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

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