# CVE-2026-46407: Vvveb: admin/auth-token IDOR allows unauthorized disclosure of administrator REST API tokens

> An authenticated administrator can access other administrators' REST API tokens via an IDOR vulnerability in the auth-token endpoint.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 15 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-5g3g-x6mf-pwr6

## What is CVE-2026-46407?

CVE-2026-46407 is a high-severity vulnerability in givanz Vvveb, published on 15 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.3, the backend admin/auth-token endpoint allows an authenticated administrator to load another administrator's REST API token list by supplying that user's admin_id. This can disclose sensitive API tokens belonging to other administrators. This vulnerability is fixed in 1.0.8.3.

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

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


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

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

## Is CVE-2026-46407 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46407 is a high-severity vulnerability in givanz Vvveb, published on 15 May 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-46407 exists.

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

## Sources

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

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