# CVE-2026-117532: REDAXO Core 5.3.0 before 5.21.4 Authentication Bypass via History Plugin


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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-px8f-whj8-hrpq, GHSA-v3wh-4qp2-g2hm

## What is CVE-2026-117532?

CVE-2026-117532 is a critical vulnerability in redaxo core, published on 27 Oct 2026. 

### Official description

REDAXO core from 5.3.0 before 5.21.4 contains an authentication bypass vulnerability in the structure/history plugin that allows unauthenticated attackers to forge temporary login tokens. Attackers can force the session-tied secret into a predictable state and forge tokens for accounts like admin, gaining backend access and code execution outside live mode.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-117532 being exploited?

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

Public exploit code:

- PoC for CVE-2026-117532 in REDAXO Authentication bypass, full chain not yet implemented. CVSS score 9.3 critical (github_poc): https://github.com/asvorg/CVE-2026-117532-poc

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117532 is a critical vulnerability in redaxo core, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117532 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-117532/ (Markdown: https://insights.sbomify.com/CVE-2026-117532/index.md)
```

## Sources

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

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