/

CVE-2026-77915

Severity:

CRITICAL RISK

(9.8)

Authentication Bypass (CWE-306) in rConfig Core Admin

CVE-2026-77915

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-306, CWE-1188

Impact:

Unauthenticated administrative account takeover

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical authentication bypass in rConfig Core allows unauthenticated attackers to register accounts that receive Administrator privileges by default. Successful abuse may expose stored device credentials and user data, and may allow attackers to issue API tokens.

Affected context

The vulnerability occurs in rConfig Core deployments where a duplicate authentication route declaration re-enables account registration after the registration endpoint was intended to be disabled. It is especially risky when newly created users inherit the default Admin role and administrative access is not explicitly assigned or restricted during registration.

Exploit preconditions

  • Attack surface: Public web application registration functionality
  • Required access: No prior authentication or account is required
  • Trigger point: Account creation through the re-enabled registration route
  • Why exploitation is possible: Registration remains reachable, while the

user creation flow does not explicitly assign a restricted role and the

database default grants Administrator privileges

Why this happens

The underlying issue is an authentication and authorization design failure caused by conflicting route configuration. A duplicate generic authentication route declaration restores a registration endpoint that was explicitly disabled, while the registration logic relies on an unsafe database default instead of assigning a least-privileged role. This maps primarily to CWE-306: Missing Authentication for Critical Function, with a related CWE-1188: Insecure Default Initialization of Resource, because an unauthenticated user can obtain privileged access through an insecure default.

Potential impact

  • Attackers may create unauthorized Administrator accounts
  • Attackers could access stored device credentials and sensitive user data
  • Attackers may issue API tokens with administrative capabilities
  • Attackers could alter application settings, users, or managed devices
  • Compromise may enable broader network access through exposed credentials

General mitigation guidance

Mitigation generally focuses on making registration and authorization

behavior explicit and secure by default.

Common defensive patterns include:

  • Disable public registration unless it is an intentional business requirement
  • Remove conflicting or duplicate route declarations and enforce route policy centrally
  • Assign new accounts an explicit least-privileged role during creation
  • Avoid privileged database defaults for security-sensitive fields
  • Require administrative approval or verified enrollment for account provisioning
  • Apply least privilege to application roles, API tokens, and stored credentials
  • Protect sensitive credentials with appropriate encryption and access controls
  • Treat administrative endpoints and token issuance as authenticated operations

How teams detect issues like this

Organizations can identify similar weaknesses through:

  • Static analysis for duplicate route registration and publicly exposed auth endpoints
  • Code review checks ensuring disabled routes are not reintroduced elsewhere
  • Review of user-creation logic for missing explicit role assignment
  • Database schema reviews for privileged defaults in authorization fields
  • Integration tests verifying unauthenticated users cannot register or reach admin functions
  • Runtime monitoring for unexpected account creation, privilege assignment, and API token issuance
  • Policy enforcement requiring authentication and authorization tests for sensitive routes

Sources

SourceLink
github.comgithub.com/rconfig/rconfig/releases#release-core-8.2.10
github.comgithub.com/rconfig/rconfig/security/advisories/GHSA-w3hx-9cxg-5ccr
vulncheck.comvulncheck.com/advisories/rconfig-unauthorized-admin-registration-via-web-php

Frequently asked

questions

Yes. The affected registration functionality is exposed through the web

application, so an attacker may not need an existing account or prior

authenticated access.

No prior access is generally required beyond network reachability to the

rConfig web interface and availability of the registration route.

Disable public registration when it is not required, remove conflicting route

definitions, and assign every new account an explicit least-privileged role

rather than relying on a privileged default.

Use centralized route policy, test authentication boundaries in CI, review

authorization defaults, monitor administrative account creation, and require

explicit authorization for token issuance and privileged operations.

Find out what's already
exploitable in your codebase.