Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2010-3204: PHP Remote File Inclusion in Pecio CMS 2.0.5

Published Sep 3, 2010 · 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.3%84th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Pecio-Cms
IdentifiersCVE-2010-3204CWE-94 · Improper Control of Generation of…

CVE-2010-3204 describes multiple remote file inclusion (RFI) vulnerabilities in Pecio CMS 2.0.5. The vulnerabilities exist in the files post.php, article.php, blog.php, and home.php within the pec_templates/nova-blue/ directory. These scripts fail to properly sanitize the 'template' parameter, allowing attackers to specify a remote URL, which is then included and executed as PHP code on the 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 target server, leading to full compromise of the affected system, including the ability to install malware, steal data, or further pivot within the network.

Mitigation

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

Restrict access to the affected PHP files via web server configuration. Disable allow_url_include and allow_url_fopen in the PHP configuration to prevent remote file inclusion. Employ input validation to ensure only trusted templates can be loaded.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version of Pecio CMS where user-supplied input is properly sanitized and validated before being used in file inclusion operations. If no patch is available, consider removing or disabling the vulnerable scripts.

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
Pecio-CmsPecio Cmsapplication
FAQ

Frequently asked questions

Is CVE-2010-3204 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2010-3204 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2010-3204?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2010-3204.
Is there a patch for CVE-2010-3204?
Upgrade to a fixed version of Pecio CMS where user-supplied input is properly sanitized and validated before being used in file inclusion operations. If no patch is available, consider removing or disabling the vulnerable scripts.
What products are affected by CVE-2010-3204?
Pecio-Cms Pecio Cms.
How severe is CVE-2010-3204?
CVE-2010-3204 has a CVSS v2 score of 7.5 (High) and an EPSS score of 2.3% (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.