# CVE-2015-20067: WP Attachment Export < 0.2.4 - Unauthenticated Posts Download

> Unauthenticated attackers can download XML data containing attachment and post details due to missing access controls in the WP Attachment Export plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 1 Nov 2021
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7579-vg8j-qmq7

## What is CVE-2015-20067?

CVE-2015-20067 is a high-severity missing authorization vulnerability in Unknown WP Attachment Export, published on 1 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Attachment Export WordPress plugin before 0.2.4 does not have proper access controls, allowing unauthenticated users to download the XML data that holds all the details of attachments/posts on a Wordpress

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Wp Attachment Export Project Wp Attachment Export.

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

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

## Is CVE-2015-20067 being exploited?

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

Public exploit code:

- WP Attachment Export < 0.2.4 - Unrestricted File Download (nuclei): http/cves/2015/CVE-2015-20067.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2015-20067 is a high-severity missing authorization vulnerability in Unknown WP Attachment Export, published on 1 Nov 2021. 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-2015-20067 exists.

Affected product: Unknown WP Attachment Export. 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-20067/ (Markdown: https://insights.sbomify.com/CVE-2015-20067/index.md)
```

## Sources

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

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