CVE-2025-2267: The WP01 plugin for WordPress is vulnerable to Arbitrary File Download in all versions up to, and including, 2

Q: How do I fix CVE-2025-2267?

wp01: upgrade to newer than 2.6.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-2267 being exploited?

CVE-2025-2267 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-2267 affect?

CVE-2025-2267 affects wp01. Severity is medium (CVSS 6.5). 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 au

Q: How urgent is CVE-2025-2267?

Priority 30/100. No elevated risk signals yet.

Routine

MEDIUM 6.5UPGRADE

CVE-2025-2267 is a medium-severity flaw (CVSS 6.5) affecting wp01. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-862
Published	2025-03-15
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wp01ru

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-15 04:15 UTCPublished CVE record published
2026-06-17 09:06 UTCUpdated Record last modified

wp01ru wp01 UPGRADE

Affected: <= 2.6.2

Fixed in: newer than 2.6.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp01 || rpm -q wp01 || wp01 --version

2. UPGRADE to newer than 2.6.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp01

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp01

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-2267?

wp01: upgrade to newer than 2.6.2. Exact commands for each OS are on this page.

Is CVE-2025-2267 being exploited?

CVE-2025-2267 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-2267 affect?

CVE-2025-2267 affects wp01. Severity is medium (CVSS 6.5). 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 au

How urgent is CVE-2025-2267?

Priority 30/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs