Skip to main content
Menu
CVEs

RuoYi improper input validation in user registration endpoint

CVE-2026-132286Published November 19, 2026, updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

The user registration endpoint in yangzongzhuan RuoYi does not properly validate the deptId, status, userId, and createBy values it receives. An attacker can reach it remotely, without logging in.

Written by a model

Original description

A security vulnerability has been detected in yangzongzhuan RuoYi up to 4.8.3. The impacted element is an unknown function of the file ruoyi-admin/src/main/java/com/ruoyi/web/controller/system/SysLoginController.java of the component User Registration Endpoint. The manipulation of the argument deptId/status/userId/createBy leads to improper input validation. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The identifier of the patch is d7ad977c9ca64e9b081c893ec56fe08f51f66698. It is recommended to apply a patch to fix this issue.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-132286 (yangzongzhuan RuoYi User Registration Endpoint SysLoginController.java input validation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132286 (entry last updated 2026-11-19):
Affected:
- yangzongzhuan RuoYi: versions 4.8.0, 4.8.1, 4.8.2, 4.8.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132286 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132286 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/yangzongzhuan/RuoYi/commit/d7ad977c9ca64e9b081c893ec56fe08f51f66698
- https://vuldb.com/vuln/439656
- https://vuldb.com/vuln/439656/cti
- https://vuldb.com/cve/CVE-2026-132286
- https://vuldb.com/submit/1045030
- https://github.com/yangzongzhuan/RuoYi/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132286
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132286"}.

Affected versions

cve.now Index

24Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 9

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132286
RecordNVD · CVE-2026-132286
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · yangzongzhuan/RuoYi · Issue #339
Other links 6
AdvisoryVulDB · Advisory #439656
AdvisoryVulDB · Threat intelligence #439656
AdvisoryVulDB · CVE-2026-132286 record
AdvisoryVulDB · Submission #1045030
PatchGitHub · yangzongzhuan/RuoYi · Commit d7ad977c
RepositoryGitHub · yangzongzhuan/RuoYi · Repository

Questions about CVE-2026-132286

Is CVE-2026-132286 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-132286?

RuoYi: versions 4.8.0, 4.8.1, 4.8.2, 4.8.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.