# CVE-2026-63102: rConfig Core < 8.2.8 Privilege Escalation via Users API role field

> Authenticated users can escalate privileges to Admin by manipulating the role field in the Users API due to missing validation.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-h4rq-p45c-642r

## What is CVE-2026-63102?

CVE-2026-63102 is a medium-severity vulnerability in rConfig v8 Core, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

## Which versions are affected by CVE-2026-63102?

It affects 1 product.


Products: Rconfig Rconfig.

## How do I fix CVE-2026-63102?

No fix has been published for CVE-2026-63102 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63102 being exploited?

There is no known exploitation of CVE-2026-63102 in the wild and no public exploit code.

## Other vulnerabilities in rConfig v8 Core

- [CVE-2020-10221](https://insights.sbomify.com/CVE-2020-10221/): rConfig OS Command Injection (high 8.8, exploited in the wild)
- [CVE-2020-15715](https://insights.sbomify.com/CVE-2020-15715/): Command injection in n/a (critical 9.9)
- [CVE-2020-23151](https://insights.sbomify.com/CVE-2020-23151/): Command injection in n/a (critical 9.8)
- [CVE-2020-13638](https://insights.sbomify.com/CVE-2020-13638/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-10546](https://insights.sbomify.com/CVE-2020-10546/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63102 and fix it if it is affected.

What it is: CVE-2026-63102 is a medium-severity vulnerability in rConfig v8 Core, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63102 in the wild and no public exploit code.

Affected product: rConfig v8 Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63102/ (Markdown: https://insights.sbomify.com/CVE-2026-63102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63102
- OSV: https://osv.dev/vulnerability/CVE-2026-63102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63102/
Summaries are generated and may contain mistakes; the official description above is the record.