Skip to main content
CVE-2025-14856VulnerabilityPublished Updated

CVE-2025-14856: y_project RuoYi · Code Injection

Affects y_project RuoYiSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
y_project RuoYiAffected
  • =4.8.0
  • =4.8.1
Fixed in–

AI-suggested

1. Immediately restrict network access to the /monitor/cache/getnames endpoint using firewalls or web application firewalls (WAFs) to limit exposure to untrusted networks. 2. Implement strict input validation and sanitization on all user-supplied data, especially the argument fragment processed by the vulnerable function. 3. Monitor logs and network traffic for unusual or suspicious requests targeting the vulnerable endpoint. 4. Apply principle of least privilege to limit the permissions of services running RuoYi, reducing the impact of potential exploitation. 5. Stay alert for official patches or updates from the y_project maintainers and apply them promptly once released. 6. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect and block exploitation attempts. 7. Conduct internal audits and penetration testing to identify any exploitation or related vulnerabilities in the environment. 8. Educate development and operations teams about secure coding practices to prevent similar injection flaws in future releases.

Description

A security vulnerability has been detected in y_project RuoYi up to 4.8.1. The affected element is an unknown function of the file /monitor/cache/getnames. Such manipulation of the argument fragment leads to code injection. The attack can be executed remotely. The exploit has been disclosed publicly and may be used.

References

Community reviews

Loading reviews…