Quick answers
- Is CVE-2026-63102 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63102 being exploited in the wild.
- How severe is CVE-2026-63102?
- Medium severity, with a CVSS score of 5.4, published 20 July 2026.
- Which products and versions are affected?
- rConfig Core < 8.2.8.
- Is there a fix for CVE-2026-63102?
- A patch was published on 2026-07-17: Fix merged in pull request #325 and released in v8.2.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63102 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-63102?
- Check whether you run rConfig Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A privilege escalation vulnerability exists in rConfig Core versions prior to 8.2.8 due to improper input validation and missing authorization checks in the Users API. Specifically, the 'StoreUserRequest' component fails to validate the 'role' field against an allowlist and does not verify if the requesting user has administrative privileges before processing role assignments. An authenticated attacker can exploit this 'mass assignment' (CWE-915) vulnerability during user creation or profile updates to assign the 'Admin' role to any account, including their own. The issue is resolved in version 8.2.8 by implementing strict role validation and requiring existing administrative privileges to grant the Admin role.
Affected products
- rConfig rConfig Core < 8.2.8
Timeline
- 2026-07-17: patched: Fix merged in pull request #325 and released in v8.2.8
- 2026-07-20: disclosed: CVE published and NVD entry created