# CVE-2015-4153: Path traversal in n/a

> Remote attackers can execute arbitrary PHP files via directory traversal in the zM Ajax Login & Register plugin for WordPress.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-486g-jg8g-q4pg

## What is CVE-2015-4153?

CVE-2015-4153 is a medium-severity path traversal vulnerability in n/a, published on 10 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in the zM Ajax Login & Register plugin before 1.1.0 for WordPress allows remote attackers to include and execute arbitrary php files via a relative path in the template parameter in a load_template action to wp-admin/admin-ajax.php.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Zanematthew Zm Ajax Login \& Register.

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

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

## Is CVE-2015-4153 being exploited?

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

Public exploit code:

- WordPress Plugin zM Ajax Login & Register 1.0.9 - Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-4153 is a medium-severity path traversal vulnerability in n/a, published on 10 Jun 2015. 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-2015-4153 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-4153/ (Markdown: https://insights.sbomify.com/CVE-2015-4153/index.md)
```

## Sources

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

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