CVE-2009-3597 is an information-disclosure vulnerability in Digitaldesign CMS 0.1. The application stores its database file, containing sensitive information, beneath the web root without sufficient access control. A remote requester can directly retrieve that file rather than accessing it through intended application functionality.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An information-disclosure vulnerability in Digitaldesign CMS 0.1 caused by storing sensitive data, including a database file, beneath the web root with insufficient access controls. Remote unauthenticated attackers can retrieve the file directly via autoconfig.dd.
Insufficient access control in a web application exposes a database file under the web root to direct request.
Insufficient access control over a database file placed under a web root permits direct access.
An access control vulnerability in a web application where a database file is stored under the web root and can be directly requested.
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.