# CVE-2026-45563: Roxy-WI: IDOR — any authenticated user can read another user's full action history

> Any authenticated user can read another user's full action history due to missing authorization checks in the history endpoint.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-wcmc-cjmw-54x9

## What is CVE-2026-45563?

CVE-2026-45563 is a medium-severity missing authorization vulnerability in roxy-wi, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. In versions 8.2.6.4 and prior, GET /history/<service>/<server_ip> re-uses the server_ip path parameter as a user-id when service == 'user', with no authorization check. Any authenticated user — even a guest in an unrelated group — can list any other user's full action audit trail (server IPs touched, configs deployed, services restarted). At time of publication, there are no publicly available patches.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-45563 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45563 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45563 is a medium-severity missing authorization vulnerability in roxy-wi, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45563 exists.

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

## Sources

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

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