CVE-2013-10054 is an unauthenticated arbitrary file upload vulnerability in LibrettoCMS version 1.1.7, and possibly earlier versions, affecting the File Manager plugin. The vulnerable upload handler is located at adm/ui/js/ckeditor/plugins/pgrfilemanager/php/upload.php. The handler does not properly validate uploaded file extensions, which allows an attacker to upload a file using a misleading or non-executable extension and then rename it to a .php script. Because the uploaded PHP file can then be executed by the web server, the issue results in unauthenticated remote code execution on the target server.
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 single Metasploit module (libretto_upload_exec.rb) that exploits an arbitrary file upload vulnerability in LibrettoCMS 1.1.7 and possibly earlier versions. The exploit works by uploading a malicious PHP payload disguised as a .pdf file to the vulnerable file manager component, then renaming it to a .php extension, and finally executing it to achieve remote code execution. The module is fully integrated with Metasploit, allowing for customizable payloads and automated exploitation. The main endpoints targeted are the file upload and file rename scripts within the LibrettoCMS installation. The exploit is weaponized, as it is part of the Metasploit framework and supports a variety of payloads. The code is written in Ruby and leverages Metasploit's HTTP client and PHP payload generation capabilities.
4 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.