Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2005-3584: XSS in PhpWebThings 1.4.4 forum.php

Published Nov 16, 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.4%73rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Phpwebthings
IdentifiersCVE-2005-3584CWE-80

CVE-2005-3584 is a cross-site scripting (XSS) vulnerability in PhpWebThings version 1.4.4, specifically in the forum.php file. The vulnerability allows remote attackers to inject arbitrary web script or HTML via the 'forum' parameter. Exploitation requires user interaction but does not require authentication, and the vulnerability is classified as CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page).

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 JavaScript or HTML in the context of the user's browser session, potentially leading to session hijacking, defacement, or redirection to malicious sites. The vulnerability impacts the integrity of affected systems but does not provide direct access to the underlying server.

Mitigation

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

As a mitigation, administrators should implement input validation and output encoding for user-supplied data in the 'forum' parameter. Additionally, deploying web application firewalls (WAFs) with XSS filtering capabilities can help reduce the risk of exploitation. Disabling or restricting access to forum.php may also be considered until a fix is available.

Remediation

Patch, then assume compromise.

No official remediation or patch is known for this vulnerability. Users should consider upgrading to a newer version of PhpWebThings if available, or apply input validation and output encoding to the 'forum' parameter in forum.php to prevent script injection.

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

Frequently asked questions

Is CVE-2005-3584 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2005-3584 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2005-3584?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2005-3584.
Is there a patch for CVE-2005-3584?
No official remediation or patch is known for this vulnerability. Users should consider upgrading to a newer version of PhpWebThings if available, or apply input validation and output encoding to the 'forum' parameter in forum.php to prevent script injection.
What products are affected by CVE-2005-3584?
Phpwebthings.
How severe is CVE-2005-3584?
CVE-2005-3584 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 1.4% (73rd 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.