# CVE-2007-5653: Security feature bypass in n/a

> Attackers can bypass PHP safe_mode and disable_functions restrictions on Windows to execute arbitrary commands and escalate privileges.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wrw6-82r7-m5c2

## What is CVE-2007-5653?

CVE-2007-5653 is a critical vulnerability in Php Php, published on 23 Oct 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2007-5653?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2007-5653?

No fix has been published for CVE-2007-5653 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-5653 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5653 exists.

Public exploit code:

- PHP 5.x COM - Safe Mode / disable_functions Bypass (exploitdb)

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5653 and fix it if it is affected.

What it is: CVE-2007-5653 is a critical vulnerability in Php Php, published on 23 Oct 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5653 exists.

Affected product: Php Php. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-5653/ (Markdown: https://insights.sbomify.com/CVE-2007-5653/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-5653
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-5653
- OSV: https://osv.dev/vulnerability/CVE-2007-5653

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-5653/
Summaries are generated and may contain mistakes; the official description above is the record.