External risk intelligence

Vvveb CMS Authenticated IDOR on Auth-Token Endpoint

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-112905

Vvveb is a CMS designed for building websites and e-commerce stores, which are commonly deployed as public-facing web applications. Because the vulnerable administrative endpoint is part of a web-based management interface for an internet-exposed application, it is commonly reachable in standard deployment patterns.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Vvveb, a website building platform, allows authenticated administrators to access and modify other administrators' API tokens. This could potentially compromise sensitive information or control over the platform's functionalities.

  • Admins can misuse API tokens.
  • Secures administrative access and data integrity.
  • Verify Vvveb administrator exposure.

Attack Path

How an attacker could exploit the issue

An attacker with administrator privileges could access the authentication token management feature. By exploiting an Insecure Direct Object Reference vulnerability on this endpoint, they can view or modify the API tokens of other administrators. This access could allow them to impersonate other administrators or disrupt critical system functions.

  • Requires authenticated administrator access.
  • Insecure Direct Object Reference on auth-token endpoint.
  • Unauthorized API token access and modification.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an administrator to view and modify another administrator's API tokens on the Vvveb CMS. This could occur when an authenticated administrator accesses the `admin/auth-token` endpoint, which may lead to unauthorized access or modification of services integrated with these tokens.

  • Administrator API tokens at risk.
  • Via authenticated access to specific endpoint.
  • Unauthorized access to integrated services.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Vvveb CMS deployments, likely managed by platform or application owners. The immediate first step is to identify all instances of Vvveb, confirm their exposure and business criticality, and then assign ownership for remediation, potentially involving coordination with web infrastructure teams.

  • Platform or application owners should lead.
  • Verify Vvveb instances and exposure.
  • Plan risk-based remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Vvveb CMS?

Vvveb is a web content management system that includes an integrated page builder. It is designed to help users construct websites, blogs, and online stores by providing a user-friendly interface for managing site structure and digital content without needing deep coding knowledge.

How does CVE-2026-112905 work?

This vulnerability is an Insecure Direct Object Reference (IDOR), classified as CWE-285. It occurs because the system fails to properly verify if an administrator has permission to access specific records. Consequently, an attacker can manipulate the system to view or change another administrator's API tokens.

Does this vulnerability trigger automatically?

No. The issue is not triggered by mere access to the website. It requires an attacker to already have valid administrator credentials and to specifically target the admin/auth-token endpoint. If an attacker lacks administrative login rights, this specific path remains inaccessible.

Is my Vvveb instance at risk?

According to Halo Surface Signal, Vvveb installations are often deployed as public-facing web applications. Since the administrative management interface is typically reachable over the internet in standard setups, your instance is likely accessible to network-based threats if it is not properly restricted.

What should I do to secure my system?

The primary response is to update your Vvveb installation to version 1.0.8.7 or later, which contains the fix for this issue. Before patching, identify all instances of the CMS in your environment, determine their criticality, and ensure you have an update plan ready to apply the version containing the security improvement.

References