Medium

Cross-Site Scripting in Cacti 0.8.7e

IdentifiersCVE-2009-4032CWE-79· Improper Neutralization of Input…

CVE-2009-4032 is a set of multiple cross-site scripting vulnerabilities in Cacti 0.8.7e. The flaws affect several PHP components, including graph rendering and UI-related code paths associated with graph.php, include/top_graph_header.php, lib/html_form.php, and lib/timespan_settings.php. Insufficient validation or output encoding of user-supplied input allows remote attackers to inject arbitrary web script or HTML through crafted request parameters, including parameters used for graph date ranges, tree actions, refresh behavior, and pane width settings. Successful exploitation results in script execution in the browser of a user interacting with the affected Cacti web interface.

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 an attacker to execute arbitrary script in the context of the affected Cacti application within a victim user's browser session. This can enable session hijacking, theft of application data visible to the victim, unauthorized actions performed with the victim's privileges, interface manipulation, and delivery of further client-side payloads. Impact depends on the privileges of the targeted user, with administrative users presenting the highest risk.

Mitigation

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

If immediate patching is not possible, restrict access to the Cacti web interface to trusted administrators and management networks, reduce exposure of the application to untrusted users, and monitor for suspicious requests containing script payloads in graph, date, refresh, or UI-related parameters. Additional defensive measures include enforcing strong session protections and using browser-side controls such as Content Security Policy where feasible, though these do not replace patching.

Remediation

Patch, then assume compromise.

Upgrade Cacti to a fixed version provided by the vendor or downstream distributor. Debian fixes were issued in updated package versions for supported releases. Apply the latest available security update for the deployed branch and verify that all affected PHP components are replaced with patched versions that properly validate and encode user-controlled input.

PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 2 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

CactiCactiapplication

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

ACTIVITY FEED

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

1 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

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