# CVE-2026-14736: Ruijie RG-UAC user_auth_commit.php unrestricted upload

> Remote attackers can upload arbitrary files via the upload_image parameter in user_auth_commit.php, potentially leading to code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-cvqg-vphp-rf28

## What is CVE-2026-14736?

CVE-2026-14736 is a medium-severity vulnerability in Ruijie RG-UAC, published on 5 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Ruijie RG-UAC up to 1.0-R1.8.2.p5. The impacted element is an unknown function of the file user_auth_commit.php. Performing a manipulation of the argument upload_image results in unrestricted upload. The attack is possible to be carried out remotely. The exploit has been made public and could be used.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-14736 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14736 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14736 is a medium-severity vulnerability in Ruijie RG-UAC, published on 5 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14736 exists.

Affected product: Ruijie RG-UAC. 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-14736/ (Markdown: https://insights.sbomify.com/CVE-2026-14736/index.md)
```

## Sources

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

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