# CVE-2014-8731: Deserialization in n/a

> Remote attackers can execute arbitrary PHP code by exploiting unsafe deserialization in PHPMemcachedAdmin, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3mrx-5p8g-6q5j

## What is CVE-2014-8731?

CVE-2014-8731 is a critical unsafe deserialization vulnerability in n/a, published on 23 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHPMemcachedAdmin 1.2.2 and earlier allows remote attackers to execute arbitrary PHP code via vectors related "serialized data and the last part of the concatenated filename," which creates a file in webroot.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2014-8731?

It affects 1 product.


Products: Phpmemcachedadmin Project Phpmemcachedadmin.

## How do I fix CVE-2014-8731?

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

## Is CVE-2014-8731 being exploited?

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

Public exploit code:

- CVE-2014-8731 - PHPMemcachedAdmin RCE - Proof of Concept (github_poc): https://github.com/sbani/CVE-2014-8731-PoC

## Other vulnerabilities in n/a

- [CVE-2014-8732](https://insights.sbomify.com/CVE-2014-8732/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8731 and fix it if it is affected.

What it is: CVE-2014-8731 is a critical unsafe deserialization vulnerability in n/a, published on 23 Mar 2017. 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-2014-8731 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-2014-8731/ (Markdown: https://insights.sbomify.com/CVE-2014-8731/index.md)
```

## Sources

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

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