High

Unrestricted File Upload in phpBP RC3 (2.204)

IdentifiersCVE-2007-0370CWE-434

CVE-2007-0370 describes an unrestricted file upload vulnerability in phpBP RC3 (2.204) and earlier. The vulnerability exists in index.php, where remote administrators can upload arbitrary PHP code via the image_form parameter during a banners add operation. By using a filename with multiple extensions (e.g., .jpg.vil.gif.php), the uploaded file is stored in the upload/banners/ directory under a different name but remains executable via direct request. This allows attackers to inject and execute arbitrary PHP code on the server. Additionally, a separate SQL injection vulnerability could be exploited to allow unauthenticated remote attackers to reach this file upload vector.

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.

Successful exploitation allows remote attackers to execute arbitrary PHP code on the server, leading to full compromise of the affected system. If chained with the referenced SQL injection vulnerability, unauthenticated attackers could gain remote code execution without valid credentials.

Mitigation

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

Implement server-side validation to restrict file uploads to safe file types and reject files with multiple extensions or executable content. Configure the web server to prevent execution of uploaded files in the upload/banners/ directory. Monitor and audit file uploads for suspicious activity. Restrict access to the upload/banners/ directory as much as possible.

Remediation

Patch, then assume compromise.

Upgrade to a version of phpBP that properly validates and restricts file uploads, ensuring only allowed file types are accepted and executable files cannot be uploaded. Apply any available patches from the vendor addressing this issue. Additionally, address the referenced SQL injection vulnerability to prevent unauthenticated access.

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

PhpbpPhpbpapplication

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

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

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