Skip to main content
Mallory
HighVulnerability

CVE-2006-2521: Remote File Inclusion in phpMyDirectory cron.php

Published May 22, 2006 · 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.8%87th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Accomplishtechnology
IdentifiersCVE-2006-2521CWE-94 · Improper Control of Generation of…

A remote file inclusion vulnerability exists in phpMyDirectory 10.4.4 and earlier, specifically in the cron.php script. The vulnerability is due to insufficient sanitization of the ROOT_PATH parameter, which allows remote attackers to include and execute arbitrary PHP code by supplying a malicious URL.

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 PHP code on the server, potentially leading to full compromise of the affected system, including data theft, defacement, or use as a pivot point for further attacks.

Mitigation

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

As an immediate mitigation, disable remote file inclusion in the PHP configuration (e.g., set 'allow_url_include=Off' and 'allow_url_fopen=Off'), and restrict access to cron.php via web server configuration until the application can be patched.

Remediation

Patch, then assume compromise.

Upgrade to a version of phpMyDirectory later than 10.4.4 where this vulnerability is patched. Ensure that all user-supplied input is properly validated and sanitized before use in file inclusion operations.

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
AccomplishtechnologyPhpmydirectoryapplication
FAQ

Frequently asked questions

Is CVE-2006-2521 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2006-2521 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2006-2521?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2006-2521. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2006-2521?
Upgrade to a version of phpMyDirectory later than 10.4.4 where this vulnerability is patched. Ensure that all user-supplied input is properly validated and sanitized before use in file inclusion operations.
What products are affected by CVE-2006-2521?
Accomplishtechnology Phpmydirectory.
How severe is CVE-2006-2521?
CVE-2006-2521 has a CVSS v2 score of 7.5 (High) and an EPSS score of 2.8% (87th 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.