HighPublic exploit

Arbitrary PHP Code Execution via Double-Extension Upload in DeluxeBB

IdentifiersCVE-2006-4558CWE-434· Unrestricted Upload of File with…

DeluxeBB 1.06 and earlier contains an unrestricted dangerous file-upload vulnerability when deployed on Apache HTTP Server with mod_mime. The new-thread upload functionality accepts attacker-supplied files with double extensions, allowing a PHP extension to remain active in the generated filename. An attacker can upload a PHP payload that Apache processes as PHP code.

For your environment

Are you exposed to this one?

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.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

A remote attacker can achieve arbitrary PHP code execution in the context of the web-server PHP process. The resulting impact depends on that process's permissions and may permit unauthorized application or server actions.

Mitigation

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

Restrict uploads to a small server-side allowlist of required, non-executable file types; reject filenames containing multiple extensions; generate server-side filenames rather than retaining user-controlled names; and store uploaded content outside the web document root. Configure the web server so uploaded content cannot be interpreted as PHP, and run upload-handling and PHP processes with least privilege.

Remediation

Patch, then assume compromise.

Upgrade DeluxeBB to a version that corrects file upload validation, if available. Implement strict server-side allowlisting of permitted upload types and reject executable server-side script extensions, including double-extension and mixed-case variants. Generate server-side filenames rather than preserving user-supplied names, and store uploaded content outside the web document root so it cannot be executed directly by the web server. Review Apache and mod_mime handling to ensure uploaded content cannot be mapped to executable PHP processing based on residual or inner extensions.

PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

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

DeluxebbDeluxebbapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app

cwe mitreNews

Dec 28, 2009

CWE - CWE-434: Unrestricted Upload of File with Dangerous Type (4.20)

An observed example where a double .php extension bypass left an active PHP extension in the generated filename, enabling dangerous upload behavior.

cwe mitreNews

Jul 19, 2006

CWE - CWE-434: Unrestricted Upload of File with Dangerous Type (4.19.1)

A file upload vulnerability involving a double .php extension that results in an active PHP extension in the generated filename, enabling dangerous file handling.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity