# CVE-2015-4338: Code injection in n/a

> Authenticated users can inject arbitrary PHP code into language files in the XCloner WordPress plugin, leading to remote code execution.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 17 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mxw2-9c4g-5hgw

## What is CVE-2015-4338?

CVE-2015-4338 is a medium-severity code injection vulnerability in n/a, published on 17 Jun 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Static code injection vulnerability in the XCloner plugin 3.1.2 for WordPress allows remote authenticated users to inject arbitrary PHP code into the language files via a Translation LM_FRONT_* field for a language, as demonstrated by language/italian.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2015-4338?

It affects 1 product.


Products: Xcloner Xcloner.

## How do I fix CVE-2015-4338?

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

## Is CVE-2015-4338 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-35948](https://insights.sbomify.com/CVE-2020-35948/): Missing authorization in n/a (critical 9.9)
- [CVE-2020-35950](https://insights.sbomify.com/CVE-2020-35950/): Cross-site request forgery in n/a (critical 9.8)
- [CVE-2014-2579](https://insights.sbomify.com/CVE-2014-2579/): Cross-site request forgery in n/a (high 7.6)
- [CVE-2014-2996](https://insights.sbomify.com/CVE-2014-2996/): Command injection in n/a (high 7.1)
- [CVE-2014-2340](https://insights.sbomify.com/CVE-2014-2340/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4338 and fix it if it is affected.

What it is: CVE-2015-4338 is a medium-severity code injection vulnerability in n/a, published on 17 Jun 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-4338 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-2015-4338/ (Markdown: https://insights.sbomify.com/CVE-2015-4338/index.md)
```

## Sources

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

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