Skip to main content
VulnerabilityPublished

CVE-2024-46076: RuoYi · Code Injection

Affects RuoYiSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2024

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubyangzongzhuan/RuoYipkg:github/yangzongzhuan/RuoYiOther threatsAffected
  • <=4.7.9
Fixed in–

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

AI-suggested

To mitigate CVE-2024-46076, organizations should: 1) Immediately upgrade to a patched version of RuoYi once available; monitor vendor announcements for official patches. 2) If patches are not yet available, disable or restrict access to the code generation feature, especially from untrusted networks. 3) Implement strict input validation and sanitization on all inputs to the code generation module to prevent injection of malicious code. 4) Employ network segmentation and firewall rules to limit exposure of development and build environments. 5) Monitor logs and network traffic for unusual activity related to code generation requests or unexpected code changes. 6) Conduct code reviews and static analysis to detect injection flaws in customizations or extensions. 7) Use runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect and block suspicious execution patterns. 8) Educate developers and administrators about secure coding practices and the risks of code injection vulnerabilities. These measures collectively reduce the risk of exploitation until a formal patch is applied.

Description

RuoYi v4.7.9 and before has a security flaw that allows escaping from comments within the code generation feature, enabling the injection of malicious code.

References

Community reviews

Loading reviews…