Skip to main content
VulnerabilityPublished Updated

CVE-2026-57949: Yunai ruoyi-vue-pro · Missing Authorization

Affects Yunai ruoyi-vue-proSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Yunairuoyi-vue-proAffected
  • <=2026.05
Fixed in–
GitHubruoyi-vue-propkg:github/ruoyi-vue-proOther threatsAffected
  • <=2026.05
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The vulnerability is reportedly fixed in commit c779a47, so applying the corresponding update or patch from the vendor is recommended once available. Until then, restrict access to the affected endpoint to trusted users only and monitor for suspicious activity involving sequential ID enumeration.

Description

ruoyi-vue-pro through 2026.05, fixed in commit c779a47, contains a missing authorization vulnerability in the CRM module's GET /admin-api/crm/follow-up-record/get endpoint that allows authenticated users to read any follow-up record by iterating sequential numeric IDs. Attackers can exploit this by sending requests with arbitrary ID parameters to access other users' follow-up notes, file attachments, scheduling information, and business entity references without proper authorization checks.

References

Community reviews

Loading reviews…