dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-46407

HIGH · 8.1 CVSS v3.1 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The backend admin/auth-token endpoint in Vvveb CMS prior to 1.0.8.3 allows an authenticated administrator to retrieve another administrator's REST API token list by directly specifying that user's admin_id parameter, resulting in an Insecure Direct Object Reference (IDOR) that exposes sensitive API tokens belonging to other administrators.

MitigationUpgrade to Vvveb 1.0.8.3 or later to obtain the patch, and immediately rotate any API tokens that may have been exposed prior to applying the fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Vvveb CMS installation
    Identify if the web application is Vvveb CMS by examining the application footer, login page, or checking for Vvveb-specific file structures or cookies
    Affected if The application is running Vvveb CMS
  2. Check Vvveb version
    Locate the installed version number in the administration panel footer, or check version files in the application root directory
    Affected if The version is below 1.0.8.3 (any version prior to 1.0.8.3)
  3. Verify admin user accounts exist
    Access the admin panel and navigate to the user/administrator management section to confirm multiple admin accounts exist
    Affected if There are two or more administrator accounts configured
  4. Check for REST API token configuration
    In the admin panel, locate the API settings or authentication token management area where REST API tokens are generated or stored for administrators
    Affected if The system has REST API tokens enabled or configured for admins
  5. Test IDOR vulnerability on auth-token endpoint
    Using an authenticated admin session, make a direct HTTP request to the /admin/auth-token endpoint with a different admin_id parameter to see if tokens for that other admin are returned without proper authorization
    Affected if The endpoint returns another administrator's API tokens when a different admin_id is supplied

A user is affected if they run Vvveb CMS version below 1.0.8.3 with multiple admin accounts that have REST API tokens configured, where the auth-token endpoint permits unauthorized access to other admins' tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Vvveb 1.0.8.3 or later to obtain the patch, and immediately rotate any API tokens that may have been exposed prior to applying the fix.

Recommended fix High confidence

1.0.8.3

  1. Backup the current Vvveb installation and database before proceeding with any upgrade
  2. Download Vvveb version 1.0.8.3 from the official Vvveb repository on GitHub
  3. Follow the standard Vvveb upgrade procedure to apply version 1.0.8.3
  4. Verify that the upgrade was successful by logging into the admin dashboard
  5. Test that the admin/auth-token endpoint properly enforces authorization and no longer allows accessing other administrators' API tokens

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46407 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46407 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data