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

> Attackers can bypass PHP safe_mode and disable_functions restrictions to read arbitrary files via the ionCube Loader extension.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **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:** 14 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pgrc-jfm5-7rm6

## What is CVE-2007-5447?

CVE-2007-5447 is a medium-severity vulnerability in Php Php, published on 14 Oct 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ioncube_loader_win_5.2.dll in the ionCube Loader 6.5 extension for PHP 5.2.4 does not follow safe_mode and disable_functions restrictions, which allows context-dependent attackers to bypass intended limitations, as demonstrated by reading arbitrary files via the ioncube_read_file function.

Weakness: CWE-264

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

It affects 2 products.


Products: Ioncube Php Encoder, Php Php.

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

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

## Is CVE-2007-5447 being exploited?

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

Public exploit code:

- PHP 5.2.4 ionCube - 'ioncube_read_file' Safe Mode / disable_functions Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5447 is a medium-severity vulnerability in Php Php, published on 14 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-5447 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-5447/ (Markdown: https://insights.sbomify.com/CVE-2007-5447/index.md)
```

## Sources

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

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