Loading vulnerability…
CVE-2011-10009 is a path traversal vulnerability in S40 CMS v0.4.2. The issue is present in the index.php page handler, where the p parameter is not properly sanitized before being used to resolve or include files. An attacker can supply directory traversal sequences to escape the intended web root or application directory and access arbitrary files on the underlying file system. The provided context also indicates use of a null byte to bypass file extension checks, suggesting the vulnerable code performs insufficient validation of the requested path and relies on extension-based restrictions that can be truncated at the string-handling boundary. The vulnerability is remotely exploitable and does not require authentication.
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 auxiliary scanner module (modules/auxiliary/scanner/http/s40_traversal.rb) targeting a directory traversal vulnerability in S40 CMS version 0.4.2 (CVE-2011-10009). The exploit leverages improper handling of the $pid parameter in the 'page' function, allowing attackers to retrieve arbitrary files from the server by sending a specially crafted HTTP GET request to the index.php endpoint. The module allows configuration of the base path, file to retrieve, traversal depth, and whether to save the retrieved file. The default target file is /etc/passwd. The exploit is a proof-of-concept and does not provide a shell or code execution, but demonstrates the ability to read sensitive files from the server. The code is written in Ruby and is designed to be used within the Metasploit framework.
3 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.