Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2005-2721: XSS in Foojan PHP Weblog index.php and admin.php

Published Aug 29, 2005 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS1.8%78th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Foojan
IdentifiersCVE-2005-2721CWE-79

CVE-2005-2721 describes multiple cross-site scripting (XSS) vulnerabilities in Foojan PHP Weblog, specifically in the index.php and admin.php scripts. The vulnerabilities allow remote attackers to inject arbitrary web script or HTML via the Referer field in the HTTP header, which is not properly sanitized before being rendered in the application.

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 attackers to execute arbitrary JavaScript or HTML in the context of users viewing affected pages, potentially leading to session hijacking, credential theft, or other attacks leveraging the victim's browser session.

Mitigation

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

As an interim measure, deploy a web application firewall (WAF) to filter malicious input in HTTP headers, and configure the application to avoid reflecting unsanitized header values in responses. Educate users to be cautious of suspicious links and referers.

Remediation

Patch, then assume compromise.

Update the application to properly sanitize and encode all user-supplied input, especially HTTP headers such as Referer, before rendering them in the output. Apply any vendor-supplied patches or updates addressing this issue.

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
FoojanPhp Weblogapplication
FAQ

Frequently asked questions

Is CVE-2005-2721 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2005-2721 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2005-2721?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2005-2721.
Is there a patch for CVE-2005-2721?
Update the application to properly sanitize and encode all user-supplied input, especially HTTP headers such as Referer, before rendering them in the output. Apply any vendor-supplied patches or updates addressing this issue.
What products are affected by CVE-2005-2721?
Foojan Php Weblog.
How severe is CVE-2005-2721?
CVE-2005-2721 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 1.8% (78th 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.