Skip to main content
Mallory
HighVulnerability

CVE-2009-3064: Directory Traversal in Ve-EDIT 0.1.4 debug_php.php

Published Sep 3, 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
EPSS2.4%84th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Rein Velt
IdentifiersCVE-2009-3064CWE-22 · Improper Limitation of a Pathname…

A directory traversal vulnerability exists in Ve-EDIT 0.1.4, specifically in the debugger/debug_php.php script. The vulnerability is due to insufficient sanitization of the 'filename' parameter passed via GET requests, allowing attackers to traverse directories using '../' sequences and include arbitrary local files for execution.

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 local files on the server, potentially leading to remote code execution, information disclosure, or further compromise of the system.

Mitigation

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

As an immediate mitigation, restrict access to debugger/debug_php.php, implement input validation to disallow directory traversal patterns, and use web server configuration to prevent access to sensitive files.

Remediation

Patch, then assume compromise.

Upgrade to a version of Ve-EDIT where input validation and sanitization are properly implemented for the 'filename' parameter in debug_php.php. Ensure user-supplied input is strictly validated and directory traversal sequences are blocked.

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
Rein VeltVeditapplication
FAQ

Frequently asked questions

Is CVE-2009-3064 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-3064 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-3064?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2009-3064. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2009-3064?
Upgrade to a version of Ve-EDIT where input validation and sanitization are properly implemented for the 'filename' parameter in debug_php.php. Ensure user-supplied input is strictly validated and directory traversal sequences are blocked.
What products are affected by CVE-2009-3064?
Rein Velt Vedit.
How severe is CVE-2009-3064?
CVE-2009-3064 has a CVSS v2 score of 7.5 (High) and an EPSS score of 2.4% (84th 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.