Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2008-2217: Directory Traversal in PHProjekt CMS 0.6.1 graphie.php

Published May 14, 2008 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.8Medium · v2
EPSS1.8%80th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Mariovaldez
IdentifiersCVE-2008-2217CWE-22 · Improper Limitation of a Pathname…

A directory traversal vulnerability exists in the graphie.php component of Content Management System 0.6.1 for PHProjekt. The vulnerability is due to insufficient sanitization of the 'cm_imgpath' parameter, which allows remote attackers to include and execute arbitrary local files by supplying directory traversal sequences (..).

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 or commands on the server by including local files, potentially leading to full system compromise depending on the privileges of the web server process.

Mitigation

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

Restrict access to the vulnerable script, use web server configuration to block requests containing directory traversal patterns, and ensure that the web server runs with minimal privileges to limit the impact of exploitation.

Remediation

Patch, then assume compromise.

Upgrade to a version of Content Management System for PHProjekt where input validation is properly implemented for the 'cm_imgpath' parameter, or apply a patch that ensures user-supplied input is sanitized to prevent directory traversal.

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
MariovaldezContent Management Systemapplication
FAQ

Frequently asked questions

Is CVE-2008-2217 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-2217 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-2217?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2008-2217.
Is there a patch for CVE-2008-2217?
Upgrade to a version of Content Management System for PHProjekt where input validation is properly implemented for the 'cm_imgpath' parameter, or apply a patch that ensures user-supplied input is sanitized to prevent directory traversal.
What products are affected by CVE-2008-2217?
Mariovaldez Content Management System.
How severe is CVE-2008-2217?
CVE-2008-2217 has a CVSS v2 score of 6.8 (Medium) and an EPSS score of 1.8% (80th 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.