# CVE-2025-2267: WP01 – Speed, Security, SEO consultant <= 2.6.2 - Authenticated (Subscriber+) Arbitrary File Download

> Authenticated subscribers can download arbitrary server files due to missing capability checks in the WP01 WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 15 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-gcfr-fvmf-668m

## What is CVE-2025-2267?

CVE-2025-2267 is a medium-severity path traversal vulnerability in wp01ru WP01 – Speed, Security, SEO consultant, published on 15 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP01 plugin for WordPress is vulnerable to Arbitrary File Download in all versions up to, and including, 2.6.2 due to a missing capability check and insufficient restrictions on the make_archive() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to download and read the contents of arbitrary files on the server, which can contain sensitive information. CVE-2025-30567 is a duplicate of this issue.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-2267?

It affects 1 product.


Products: Wp01ru Wp01.

## How do I fix CVE-2025-2267?

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

## Is CVE-2025-2267 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2267 and fix it if it is affected.

What it is: CVE-2025-2267 is a medium-severity path traversal vulnerability in wp01ru WP01 – Speed, Security, SEO consultant, published on 15 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2267 in the wild and no public exploit code.

Affected product: wp01ru WP01 – Speed, Security, SEO consultant. 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-2025-2267/ (Markdown: https://insights.sbomify.com/CVE-2025-2267/index.md)
```

## Sources

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

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