# CVE-2011-4718: Auth bypass in n/a

> Remote attackers can hijack web sessions by specifying a session ID, requiring user interaction to exploit.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Aug 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-36c7-4qpg-3rf4

## What is CVE-2011-4718?

CVE-2011-4718 is a medium-severity authentication bypass vulnerability in Php Php, published on 13 Aug 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Session fixation vulnerability in the Sessions subsystem in PHP before 5.5.2 allows remote attackers to hijack web sessions by specifying a session ID.

Weakness: CWE-264

## Which versions are affected by CVE-2011-4718?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2011-4718?

Upgrade to a fixed version.

## Is CVE-2011-4718 being exploited?

There is no known exploitation of CVE-2011-4718 in the wild and no public exploit code.

## 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-2011-4718 and fix it if it is affected.

What it is: CVE-2011-4718 is a medium-severity authentication bypass vulnerability in Php Php, published on 13 Aug 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-4718 in the wild and no public exploit code.

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-2011-4718/ (Markdown: https://insights.sbomify.com/CVE-2011-4718/index.md)
```

## Sources

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

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