CVE-2025-14388
PhastPress WordPress plugin vulnerability
- Published23 Dec 2025
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://plugins.trac.wordpress.org/browser/phastpress/tags/3.6/sdk/phast.php#L9570
- https://plugins.trac.wordpress.org/browser/phastpress/tags/3.6/sdk/phast.php#L9597
- https://plugins.trac.wordpress.org/browser/phastpress/tags/3.6/sdk/phast.php#L9608
- https://plugins.trac.wordpress.org/browser/phastpress/tags/3.6/sdk/phast.php#L9641
- https://plugins.trac.wordpress.org/changeset/3418139
- https://www.wordfence.com/threat-intel/vulnerabilities/id/eec9bbc0-5a68-4624-a672-bd6227d6fa45?source=cve
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-14388 being actively exploited?
CVE-2025-14388 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.48%.
How severe is CVE-2025-14388?
CVE-2025-14388 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.48% probability of exploitation.
How do I fix CVE-2025-14388?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-14388 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.