A path traversal vulnerability exists in LimeSurvey before version 4.1.12+200324, specifically in the application/controllers/admin/LimeSurveyFileManager.php file. The vulnerability allows attackers to manipulate file paths, potentially accessing files and directories outside the intended scope of the application.
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 (1 hidden).
This repository contains a single Metasploit auxiliary scanner module targeting path traversal vulnerabilities in LimeSurvey (CVE-2020-11455 and CVE-2019-9960). The module allows an authenticated attacker to download arbitrary files from the server by exploiting vulnerable endpoints in LimeSurvey's file management and export functionality. The exploit works by sending crafted HTTP GET requests with path traversal sequences to specific endpoints, retrieving files such as /etc/passwd. The module supports multiple LimeSurvey versions and automatically determines the appropriate exploit method based on the detected version. The code is written in Ruby and is structured as a typical Metasploit module, requiring valid LimeSurvey credentials to authenticate before exploitation. The main file is 'modules/auxiliary/scanner/http/limesurvey_zip_traversals.rb', and the attack vector is network-based, targeting HTTP endpoints exposed by the LimeSurvey application.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.