LiveActive security incident?Get immediate response
CVE Record

CVE-2007-3294: Multiple buffer overflows in libtidy, as used in the Tidy extension for PHP 5.2.3 and possibly other produc...

Multiple buffer overflows in libtidy, as used in the Tidy extension for PHP 5.2.3 and possibly other products, allow context-dependent attackers to execute arbitrary code via (1) a long second argument to the tidy_parse_string function or (2) an unspecified vector to the tidy_repair_string function. NOTE: this might only be an issue in environments where vsnprintf is implemented as a wrapper for vsprintf.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old libtidy buffer overflow reported in PHP 5.2.3's Tidy extension. If a vulnerable application passes attacker-controlled data into affected Tidy functions, arbitrary code execution may be possible. The public record does not name a current patch, broad affected list, or confirmed active exploitation. Likely exposure is legacy PHP 5.2.3 deployments using the Tidy extension or other products embedding vulnerable libtidy. Exposure depends on application code passing untrusted input into affected Tidy functions and on platform implementation details. Prioritize this when legacy PHP or libtidy exists on systems that process external HTML. It is not a blanket emergency from the supplied evidence, but arbitrary code execution potential and public exploit reference justify targeted inventory and remediation. Mitigation focus: Identify PHP 5.2.3 and libtidy usage across supported and legacy systems.; Check PHP and libtidy vendor guidance for fixed versions or replacement packages.; Disable the PHP Tidy extension where it is not required..

Prepared

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-2007-3294 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
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
3Source links

CVSS and timeline data

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

Source materials

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.