LiveActive security incident?Get immediate response
CVE Record

CVE-2007-5653: The Component Object Model (COM) functions in PHP 5.x on Windows do not follow safe_mode and disable_functi...

The Component Object Model (COM) functions in PHP 5.x on Windows do not follow safe_mode and disable_functions restrictions, which allows context-dependent attackers to bypass intended limitations, as demonstrated by executing objects with the kill bit set in the corresponding ActiveX control Compatibility Flags, executing programs via a function in compatUI.dll, invoking wscript.shell via wscript.exe, invoking Scripting.FileSystemObject via wshom.ocx, and adding users via a function in shgina.dll, related to the com_load_typelib function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw affects PHP 5.x on Windows where COM functions can ignore PHP restrictions meant to limit dangerous behavior. In the wrong hosting or application context, those restrictions may not stop actions such as invoking local objects or programs. The source bundle does not name a current patch or active exploitation. Exposure is most likely in legacy PHP 5.x installations running on Windows, especially where applications or hosting environments rely on safe_mode or disable_functions as containment controls. The bundle lists affected vendor and product fields as n/a, so precise supported-version boundaries are incomplete. Treat this as a legacy-platform risk with potentially serious impact if PHP 5.x on Windows remains in use. The main business decision is whether any old Windows PHP systems still exist and whether they depend on obsolete PHP safety controls. Mitigation focus: Identify any Windows servers still running PHP 5.x.; Check PHP and platform vendor guidance for the official remediation path.; Retire or upgrade unsupported PHP 5.x deployments where feasible..

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.

cve · low confidence lookup

CVE-2007-5653 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.