# CVE-2013-7387: Auth bypass in n/a

> Remote attackers can hijack user sessions in DataLife Engine by manipulating the PHPSESSID cookie, leading to account takeover.

- **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:** No
- **Published:** 2 Jun 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6jx2-q852-9994

## What is CVE-2013-7387?

CVE-2013-7387 is a medium-severity authentication bypass vulnerability in n/a, published on 2 Jun 2014. 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 DataLife Engine (DLE) 9.7 and earlier allows remote attackers to hijack web sessions via the PHPSESSID cookie.

## Which versions are affected by CVE-2013-7387?

It affects 1 product.


Products: Dleviet Datalife Engine.

## How do I fix CVE-2013-7387?

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

## Is CVE-2013-7387 being exploited?

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

Public exploit code:

- DataLife Engine 9.7 - 'preview.php' PHP Code Injection (exploitdb)
- DataLife Engine - 'preview.php' PHP Code Injection (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-1412](https://insights.sbomify.com/CVE-2013-1412/): Code injection in n/a (high 7.5)
- [CVE-2018-14777](https://insights.sbomify.com/CVE-2018-14777/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7387 and fix it if it is affected.

What it is: CVE-2013-7387 is a medium-severity authentication bypass vulnerability in n/a, published on 2 Jun 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-7387 exists.

Affected product: n/a. 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-2013-7387/ (Markdown: https://insights.sbomify.com/CVE-2013-7387/index.md)
```

## Sources

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

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