CVE-2026-14736: Ruijie RG-UAC Unrestricted File Upload Vulnerability—Remote Exploitation Without Authentication
Ruijie RG-UAC contains a file upload vulnerability in the user_auth_commit.php script that allows unauthenticated attackers to upload arbitrary files. By manipulating the upload_image parameter, an attacker can bypass upload restrictions remotely without authentication. The vulnerability affects versions up to 1.0-R1.8.2.p5, and public exploits are available, increasing active exploitation risk.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.3 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-284, CWE-434
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-05 / 2026-07-06
NVD description (verbatim)
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.
5 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists in user_auth_commit.php where insufficient input validation on the upload_image parameter permits unrestricted file uploads. The affected administrative function fails to enforce proper access controls (CWE-284) and lacks adequate file upload restrictions (CWE-434). The attack vector is network-based with low complexity and requires no authentication or user interaction, making it trivially exploitable by remote threat actors.
Business impact
Successful exploitation enables attackers to upload malicious files (webshells, backdoors, or malware) directly onto RG-UAC appliances. This grants initial access for lateral movement into protected networks, persistent backdoor establishment, and potential compromise of network access control policy enforcement. Organizations relying on RG-UAC for network segmentation face degraded security posture if the vulnerability is exploited before patching.
Affected systems
Ruijie RG-UAC versions up to and including 1.0-R1.8.2.p5 are vulnerable. Determine your current version via the RG-UAC administrative interface and compare against the affected range. Verify whether your instance is internet-facing or isolated to internal networks, as this affects exposure timeline.
Exploitability
Exploitability is high. The attack requires no authentication, no user interaction, and no complex techniques—making it accessible to opportunistic attackers. Public exploits are confirmed available, meaning adversaries have weaponized tools ready. The CVSS 3.1 score of 7.3 (HIGH) reflects network accessibility and the ability to achieve confidentiality, integrity, and availability impacts simultaneously. Expect active reconnaissance and exploitation attempts within days of public disclosure.
Remediation
Immediately verify your RG-UAC version and confirm whether a patched release is available from Ruijie. Contact Ruijie support or consult their security advisory for the specific patch version addressing this vulnerability. Until a patch is available and deployable, implement network-level controls to restrict direct access to the RG-UAC management interface to trusted administrative networks only.
Patch guidance
Verify the latest patched version from Ruijie's official security advisory. Apply patches during a maintenance window after validating compatibility with your deployment. If a patch is not yet available, prioritize limiting network exposure of the RG-UAC appliance by implementing firewall rules to block untrusted inbound access to the administration interface. Document the patch application date and version applied for compliance records.
Detection guidance
Monitor RG-UAC logs for POST requests to user_auth_commit.php with upload_image parameters containing unexpected file types or paths. Network-level detection should flag HTTP/HTTPS traffic to the RG-UAC management port from external or unexpected sources. Inspect uploaded files in the RG-UAC web directory for recently created executables or scripts. Review authentication logs for any successful logins correlating with suspicious upload activity.
Why prioritize this
This vulnerability merits immediate attention due to the convergence of high CVSS severity (7.3), zero authentication requirement, public exploit availability, and the critical security function of the affected product. RG-UAC is a network access control appliance; compromise enables attackers to circumvent the security controls protecting your infrastructure. The low attack complexity and lack of prerequisites make this a likely candidate for widespread exploitation in coming weeks.
Risk score, explained
The CVSS 3.1 score of 7.3 reflects a network-accessible vulnerability with no authentication or user interaction barriers, coupled with multi-faceted impact: attackers can read sensitive data (confidentiality), alter system behavior through malicious uploads (integrity), and disrupt RG-UAC operations (availability). The availability of public exploits elevates real-world risk beyond the base CVSS score.
Frequently asked questions
Is my RG-UAC vulnerable?
Yes, if you are running version 1.0-R1.8.2.p5 or earlier. Check your version in the RG-UAC web interface under System or Administration settings. Newer versions are not confirmed vulnerable, but verify against Ruijie's official security bulletin to ensure you're running a patched release.
Can this vulnerability be exploited if RG-UAC is not exposed to the internet?
The vulnerability is remotely exploitable, so any attacker with network access to the RG-UAC appliance (internal network, VPN, or internet-facing) can attempt exploitation. If RG-UAC is strictly segmented to trusted administrative networks only, exploitation risk is lower but not eliminated by internal-only deployment alone.
What files can attackers upload?
The vulnerability permits unrestricted file uploads, so attackers can upload webshells, executable binaries, scripts, or any file type. They may then execute these uploads if they can access the web server directory or trigger execution through other means, potentially gaining code execution on the RG-UAC appliance.
Should I disable RG-UAC while waiting for a patch?
Disabling RG-UAC removes network access control enforcement entirely, which may violate compliance requirements or leave the network unmanaged. Instead, implement network-level access controls (firewall rules, VPN segmentation) to restrict who can reach the RG-UAC interface, then apply the patch at your earliest safe maintenance window.
This analysis is provided for informational purposes and reflects publicly available information as of the publication date. Confirm your specific product version and check Ruijie's official security advisory for the definitive patch status and recommended fixes. SEC.co does not provide guarantee regarding the completeness or accuracy of third-party vendor patch timelines. Organizations should validate patches in test environments before production deployment. This vulnerability assessment does not replace vendor guidance or your organization's risk management framework. Source: NVD (public-domain), retrieved 2026-08-14. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-11344HIGHUnrestricted File Upload in code-projects Vehicle Management System 1.0
- CVE-2026-11474HIGHUnrestricted File Upload in Kushan2k Student Management System
- CVE-2026-13547HIGHUnrestricted File Upload in Hanwang e-Face 6.3.5.4 – CVSS 7.3 HIGH
- CVE-2026-13553HIGHUnrestricted File Upload in itsourcecode Hotel Management System 1.0
- CVE-2026-10172MEDIUMBdtask Multi-Store Inventory 1.0 Unrestricted File Upload Vulnerability
- CVE-2026-10205MEDIUMUnrestricted File Upload in Metasoft MetaCRM 6.4.0 – Exploit Details & Remediation
- CVE-2026-10806MEDIUMUnrestricted File Upload in mjperpinosa stumasy
- CVE-2026-10807MEDIUMUnrestricted File Upload in mjperpinosa stumasy Profile Image Handler