CVE-2026-65891 is an improper input validation vulnerability in the file rename functionality of Joomla Content Editor (JCE) before version 2.20.2. An authenticated user with file management permissions can supply file names that should otherwise be considered invalid during rename operations. This allows the creation of hidden files and can also cause an existing file at the destination path to be unintentionally overwritten. The flaw affects file handling integrity within JCE's file management features.
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 is a small standalone Python PoC for CVE-2026-65891 affecting the Joomla Content Editor (JCE) extension. Repository structure is minimal: LICENSE, README.md, requirements.txt, and a single executable script, poc_cve_2026_65891.py. The code is not part of a larger exploit framework. The exploit targets improper input validation in JCE's file-manager rename functionality. According to the README and script header, vulnerable JCE versions prior to 2.20.2 allow an authenticated user with upload and rename permissions to rename files to dot-prefixed hidden names and potentially overwrite existing files silently. The PoC is primarily a verification tool rather than a destructive weaponized exploit. Main capabilities: 1. Bulk or single-target Joomla/JCE fingerprinting. 2. Version extraction from JCE metadata/assets to determine whether the installed version is older than 2.20.2. 3. Optional authenticated login using Joomla credentials or a supplied session cookie. 4. CSRF token extraction from Joomla pages. 5. Upload of a benign marker text file through the JCE browser/plugin RPC interface. 6. Rename of that file to a hidden dot-prefixed filename. 7. HTTP retrieval of the renamed file from the upload directory to confirm exploitation. 8. Parallel scanning with thread pool support and hit-only output logging. The script appears operational and usable: it includes CLI parsing, target normalization, concurrency, result formatting, and output handling. It is best classified as OPERATIONAL because it contains a working authenticated exploit chain with a fixed built-in marker payload, but it is not heavily modularized or framework-integrated. Fingerprintable targets and behaviors center on Joomla/JCE web paths: JCE XML manifests and TinyMCE assets for version detection, Joomla admin/frontend login flows, and the JCE RPC endpoint /index.php?option=com_jce&task=plugin.rpc&plugin=browser for upload/rename actions. Verification is performed by requesting a hidden file under /images/. Overall, the repository's purpose is to validate whether a Joomla site running vulnerable JCE can be abused by an authenticated user to create hidden files via rename, with overwrite behavior noted as part of the vulnerability.
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 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.