CVE-2026-63102

rConfig Core < 8.2.8 Privilege Escalation via Users API role field

Published Jul 20, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
rConfig Core before 8.2.8 contains a privilege escalation vulnerability that allows authenticated users to assign arbitrary roles to any account by submitting an unvalidated role field through the Users API during user creation or profile updates. Attackers can exploit the missing allowlist validation and absent admin-level authorization check in StoreUserRequest to mass-assign the Admin role directly to the User model, granting access to privileged features. rConfig Pro and Enterprise are not affected.

Analysis

AI-generated

Technical impact

rConfig Core versions earlier than 8.2.8 contain a flaw that permits authenticated users to assign any role to any account via the Users API. The lacking allow‑list validation and missing admin‑level authorization checks in StoreUserRequest enable mass‑assignment of the Admin role. This flaw elevates a normal user to a privileged account, granting access to features reserved for administrators and undermining the system’s integrity and confidentiality.

Affected Systems

The vulnerability affects rConfig rConfig Core v8 prior to 8.2.8. Versions rConfig Pro and Enterprise are not impacted. Any deployment of Core before the 8.2.8 release that allows user creation or profile updates through the public API is vulnerable.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate risk. The EPSS score below 1% suggests that exploitation is unlikely, but the vulnerability still poses a threat if an attacker gains access to a legitimate user account. The flaw is not listed in the CISA KEV catalog. Attackers can exploit the missing allow‑list validation and absent admin‑level authorization in StoreUserRequest, submitting an arbitrary role value through the Users API for user creation or profile updates. With valid credentials, an attacker can assign the Admin role to any account, elevating privileges across the system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor‑issued 8.2.8 patch or later to the rConfig Core installation
  • If patching is unavailable, disable the API endpoints that allow role modification or restrict the API to users without role assignment privileges
  • Monitor the API logs for unexpected role change attempts and audit user accounts for newly granted Admin privileges

Generated by OpenCVE AI on July 30, 2026 at 19:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:rconfig:rconfig:*:*:*:*:core:*:*:*
Type Values Removed Values Added
First Time appeared Rconfig rconfig
CPEs cpe:2.3:a:rconfig:rconfig:*:*:*:*:*:*:*:*
Vendors & Products Rconfig rconfig
Type Values Removed Values Added
First Time appeared Rconfig
Rconfig rconfig V8 Core
Vendors & Products Rconfig
Rconfig rconfig V8 Core
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description rConfig before 8.2.8 contains a privilege escalation vulnerability that allows authenticated users to assign arbitrary roles to any account by submitting an unvalidated role field through the Users API during user creation or profile updates. Attackers can exploit the missing allowlist validation and absent admin-level authorization check in StoreUserRequest to mass-assign the Admin role directly to the User model, granting access to privileged features. rConfig Core before 8.2.8 contains a privilege escalation vulnerability that allows authenticated users to assign arbitrary roles to any account by submitting an unvalidated role field through the Users API during user creation or profile updates. Attackers can exploit the missing allowlist validation and absent admin-level authorization check in StoreUserRequest to mass-assign the Admin role directly to the User model, granting access to privileged features. rConfig Pro and Enterprise are not affected.
Title rConfig < 8.2.8 Privilege Escalation via Users API role field rConfig Core < 8.2.8 Privilege Escalation via Users API role field
Type Values Removed Values Added
Description rConfig before 8.2.8 contains a privilege escalation vulnerability that allows authenticated users to assign arbitrary roles to any account by submitting an unvalidated role field through the Users API during user creation or profile updates. Attackers can exploit the missing allowlist validation and absent admin-level authorization check in StoreUserRequest to mass-assign the Admin role directly to the User model, granting access to privileged features.
Title rConfig < 8.2.8 Privilege Escalation via Users API role field
Weaknesses CWE-915
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-915

    Improperly Controlled Modification of Dynamically-Determined Object Attributes

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Jul 28, 2026, 1:05 AM
Reserved
Jul 15, 2026, 3:45 PM
Status
Analyzed
Published
Jul 20, 2026, 4:17 PM
Modified
Oct 24, 2026, 8:10 PM