# CVE-2013-5350: Deserialization in n/a

> Remote attackers can execute arbitrary PHP code via crafted serialized objects in the Remember me cookie, affecting OpenPNE users.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c26j-j6q7-r2mc

## What is CVE-2013-5350?

CVE-2013-5350 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The "Remember me" feature in the opSecurityUser::getRememberLoginCookie function in lib/user/opSecurityUser.class.php in OpenPNE 3.6.13 before 3.6.13.1 and 3.8.9 before 3.8.9.1 does not properly validate login data in HTTP Cookie headers, which allows remote attackers to conduct PHP object injection attacks, and execute arbitrary PHP code, via a crafted serialized object.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Tejimaya Openpne.

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

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

## Is CVE-2013-5350 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4333](https://insights.sbomify.com/CVE-2013-4333/): XML external entity in OpenPNE (critical 9.1)
- [CVE-2010-1040](https://insights.sbomify.com/CVE-2010-1040/): Auth bypass in n/a (medium 5.8)
- [CVE-2013-2309](https://insights.sbomify.com/CVE-2013-2309/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5350 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-5350 in the wild and no public exploit code.

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

## Sources

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

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