Skip to main content
Mallory
HighVulnerability

CVE-2009-2333: Directory Traversal and Local File Inclusion in CMS Chainuk 1.2

Published Jul 5, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS5.9%93rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Cms.Tut.Su
IdentifiersCVE-2009-2333CWE-22 · Improper Limitation of a Pathname…

CVE-2009-2333 describes multiple directory traversal vulnerabilities in CMS Chainuk 1.2 and earlier. The vulnerabilities exist in several PHP scripts (admin/admin_menu.php, index.php, admin/admin_edit.php, admin/admin_delete.php) where user-supplied parameters (menu, id) are not properly sanitized, allowing attackers to traverse directories using '..' sequences. This enables remote attackers to include and execute arbitrary local files, and in some cases, delete arbitrary files on the server. Additionally, the vector in index.php can be used for static code injection by first injecting code via the menu parameter and then including the injected file via the id parameter.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code with the privileges of the web server, potentially leading to full system compromise. Attackers can also delete arbitrary files, which may result in denial of service or further exploitation. The static code injection vector increases the risk by allowing persistent code execution.

Mitigation

If you can’t patch tonight, do this now.

As an immediate mitigation, restrict access to the vulnerable scripts (admin_menu.php, index.php, admin_edit.php, admin_delete.php) via web server configuration or authentication. Employ input validation to reject any parameters containing directory traversal sequences. Use allowlists for file inclusion and ensure the web server runs with minimal privileges.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version of CMS Chainuk where input validation and sanitization are properly implemented for all user-supplied parameters. Ensure that directory traversal sequences are filtered and that file inclusion is restricted to intended files only.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Cms.Tut.SuCms Chainukapplication
FAQ

Frequently asked questions

Is CVE-2009-2333 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-2333 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-2333?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2009-2333. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2009-2333?
Upgrade to a fixed version of CMS Chainuk where input validation and sanitization are properly implemented for all user-supplied parameters. Ensure that directory traversal sequences are filtered and that file inclusion is restricted to intended files only.
What products are affected by CVE-2009-2333?
Cms.Tut.Su Cms Chainuk.
How severe is CVE-2009-2333?
CVE-2009-2333 has a CVSS v2 score of 7.5 (High) and an EPSS score of 5.9% (93rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.