CVE-2009-4137: n/a vulnerability

CVE-2009-4137: The loadContentFromCookie function in core/Cookie.php in Piwik before 0.5 does not validate strings obtaine...

The loadContentFromCookie function in core/Cookie.php in Piwik before 0.5 does not validate strings obtained from cookies before calling the unserialize function, which allows remote attackers to execute arbitrary code or upload arbitrary files via vectors related to the __destruct function in the Piwik_Config class; php://filter URIs; the __destruct functions in Zend Framework, as demonstrated by the Zend_Log destructor; the shutdown functions in Zend Framework, as demonstrated by the Zend_Log_Writer_Mail class; the render function in the Piwik_View class; Smarty templates; and the _eval function in Smarty.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 16, 2024, 20:27 UTC (UTC+00:00)

Security readout for executives and security teams

Older Piwik versions before 0.5 could trust malicious cookie data and process it as PHP objects. A remote attacker could potentially turn that into server-side code execution or file upload. This is mainly a legacy exposure issue: any still-running Piwik 0.4.5 or earlier instance should be treated as urgent. Exposure is limited to Piwik deployments before version 0.5, especially internet-facing analytics installations that still accept user-supplied cookies. The source bundle does not identify affected CPEs or modern product names, so asset validation should focus on installed Piwik version evidence. Prioritize remediation for any live, internet-facing legacy Piwik instance. Remote code execution and file upload potential make this a high-business-impact issue, even though the available sources do not confirm active exploitation today. Mitigation focus: Upgrade Piwik to version 0.5 or later, following vendor guidance.; Retire or isolate any unsupported Piwik 0.4.5 or earlier instances.; Review web server permissions to reduce file upload and code execution impact..

Prepared: Jun 28, 2026, 09:59 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2009-4137 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 24, 2009, 16:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.