HomeWordPress vulnerabilitiesPhastPress
PhastPress vulnerabilities
PhastPress has 2 known vulnerabilities in this database. The most recent published record is dated 23 Dec 2025.
- Known vulnerabilities
- 2
- Active installs
- 10,000+
- Latest version
- 3.12
- Last updated
- 13 Aug 2026
- Most recent
- 23 Dec 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Arbitrary file read CVE-2025-14388 | Critical 9.8 | Up to 3.7 | Fixed in a later version (latest 3.12) | 23 Dec 2025 |
| Open redirect CVE-2021-24210 | Medium 6.1 | Before 1.111 | Fixed in 1.111 | 5 Apr 2021 |
Read the published descriptions
- CVE-2025-14388, 23 Dec 2025
- The PhastPress plugin for WordPress is vulnerable to Unauthenticated Arbitrary File Read via null byte injection in all versions up to, and including, 3.7. This is due to a discrepancy between the extension validation in `getExtensionForURL()` which operates on URL-decoded paths, and `appendNormalized()` which strips everything after a null byte before constructing the filesystem path. This makes it possible for unauthenticated attackers to read arbitrary files from the webroot, including wp-config.php, by appending a double URL-encoded null byte (%2500) followed by an allowed extension (.txt) to the file path. CVE record
- CVE-2021-24210, 5 Apr 2021
- There is an open redirect in the PhastPress WordPress plugin before 1.111 that allows an attacker to malform a request to a page with the plugin and then redirect the victim to a malicious page. There is also a support comment from another user one year ago (https://wordpress.org/support/topic/phast-php-used-for-remote-fetch/) that says that the php involved in the request only go to whitelisted pages but it's possible to redirect the victim to any domain. CVE record
What to do if you run PhastPress
If you run PhastPress, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new PhastPress vulnerabilities
Free. We email you when a new vulnerability is published for PhastPress, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.