Loading vulnerability…
A Server-Side Request Forgery (SSRF) vulnerability exists in the feed_parser class of Navigate CMS v2.9.4. Remote attackers can exploit this by injecting arbitrary URLs into the feed parameter, causing the server to make requests to attacker-controlled or internal resources.
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 Python exploit script (poccve2022-28117.py) and a brief README. The exploit targets Navigate CMS version 2.9.4 and earlier, specifically exploiting CVE-2022-28117, an authenticated Server-Side Request Forgery (SSRF) vulnerability. The script requires valid CMS credentials and a target URL. It first authenticates to the CMS, then abuses a dashboard feed feature to make the server fetch an arbitrary URL (defaulting to file:///etc/passwd), caches the response, and retrieves it from a predictable location. The exploit demonstrates the ability to read local files or access internal network resources via the vulnerable server. The code is a proof-of-concept and is not weaponized, but it is functional and demonstrates the vulnerability clearly. The only endpoints involved are the CMS login, the vulnerable feed endpoint, and the cache file location. The repository is straightforward, with no extraneous files or framework dependencies.
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.