CVE-2018-17254 is a SQL injection vulnerability in the JCK Editor component version 6.4.4 for Joomla!. The issue is exposed through the jtreelink/dialogs/links.php endpoint, where the parent parameter is insufficiently sanitized before being used in a database query. An attacker can supply crafted SQL syntax via this parameter to alter the intended query logic.
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 (3 hidden).
This repository contains a PHP exploit script (JCKEditor_SQLi_Exploit.php) targeting a SQL injection vulnerability (CVE-2018-17254) in the JCK Editor plugin (version 6.4.4) for Joomla. The exploit works by injecting SQL code into the 'parent' parameter of the links.php file within the Jtreelink plugin, allowing an attacker to enumerate database names, tables, columns, and dump user credentials, including administrator accounts. The script also attempts to upload a PHP web shell via MySQL's INTO OUTFILE command for remote command execution, though this requires the database to allow stacked queries and the web server to permit file writes. The README.md provides usage instructions, requirements, and context for the exploit. The main attack vector is network-based, targeting a specific HTTP endpoint. The repository is structured with a single exploit script and a README, and is operational in maturity, providing both data extraction and potential RCE capabilities.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.