Loading vulnerability…
A cross-site scripting (XSS) vulnerability exists in Ruoyi v4.7.9 and earlier, specifically in the sql parameter of the createTable() function at the /tool/gen/create endpoint. This allows attackers to inject malicious scripts that are executed in the context of a user's browser session.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for a blind SQL injection vulnerability in the RuoYi Framework (version 4.7.9 and below), specifically targeting a bypass of the CVE-2024-42900 fix. The vulnerability exists in the /tool/gen/createTable endpoint, where the 'sql' parameter is insufficiently filtered, allowing an authenticated administrator to inject arbitrary SQL commands using encoded characters (e.g., %0b instead of space). The repository consists of a README.md, which provides detailed vulnerability analysis, exploitation steps, and impact, and a Python script (ruoyi-sqli-poc.py) that automates the exploitation process. The script requires the target URL and a valid JSESSIONID cookie for authentication, and it performs blind SQL injection by sending crafted SQL payloads to the vulnerable endpoint, exfiltrating data such as the database version. The exploit is operational and demonstrates the ability to extract sensitive information from the database, highlighting the risk to affected RuoYi installations.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.