Skip to main content
Mallory
HighVulnerability

CVE-2007-0361: Remote File Inclusion in PHPMyphorum 1.5a mep/frame.php

Published Jan 19, 2007 · 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.6%86th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Comscripts
IdentifiersCVE-2007-0361CWE-94

A remote file inclusion (RFI) vulnerability exists in PHPMyphorum 1.5a, specifically in the mep/frame.php script. The vulnerability is due to insufficient sanitization of the 'chem' parameter, which allows an attacker to specify a remote URL. This can result in the inclusion and execution of arbitrary PHP code hosted on a remote server.

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 affected server, potentially leading to full system compromise, data theft, or further attacks against users and infrastructure.

Mitigation

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

Disable allow_url_fopen and allow_url_include in the PHP configuration to prevent remote file inclusion. Employ input validation and sanitization on all user-supplied parameters, especially those used in file inclusion operations.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version of PHPMyphorum where input validation and sanitization of the 'chem' parameter is properly implemented. Alternatively, apply a patch that ensures only local files can be included and that user input is strictly validated.

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

Frequently asked questions

Is CVE-2007-0361 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2007-0361 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2007-0361?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2007-0361. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2007-0361?
Upgrade to a fixed version of PHPMyphorum where input validation and sanitization of the 'chem' parameter is properly implemented. Alternatively, apply a patch that ensures only local files can be included and that user input is strictly validated.
What products are affected by CVE-2007-0361?
Comscripts Phpmyphorum.
How severe is CVE-2007-0361?
CVE-2007-0361 has a CVSS v2 score of 7.5 (High) and an EPSS score of 2.6% (86th 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.