# CVE-2013-7240: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in the Advanced Dewplayer WordPress plugin.

- **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:** Yes
- **Published:** 2 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9hc2-jgqx-ghw9, MINI-5rvw-9jq3-gppq, MINI-v8cc-rhh3-55ph

## What is CVE-2013-7240?

CVE-2013-7240 is a medium-severity path traversal vulnerability in Wordpress Wordpress, published on 2 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in download-file.php in the Advanced Dewplayer plugin 1.2 for WordPress allows remote attackers to read arbitrary files via a .. (dot dot) in the dew_file parameter.

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

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

It affects 2 products.


Products: Westerndeal Advanced Dewplayer, Wordpress Wordpress.

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

Upgrade to a fixed version.

## Is CVE-2013-7240 being exploited?

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

Public exploit code:

- WordPress Plugin Advanced Dewplayer - 'download-file.php' Script Directory Traversal (exploitdb)
- WordPress Plugin Advanced Dewplayer 1.2 - Directory Traversal (nuclei): http/cves/2013/CVE-2013-7240.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7240 is a medium-severity path traversal vulnerability in Wordpress Wordpress, published on 2 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-7240 exists.

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

## Sources

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

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