Quick answers
- Is CVE-2026-13251 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13251 being exploited in the wild.
- How severe is CVE-2026-13251?
- High severity, with a CVSS score of 7.5, published 2 July 2026.
- Which products and versions are affected?
- Perfmatters up to, and including, 2.6.4.
- Is there a fix for CVE-2026-13251?
- A patch was published on 2026-06-30: Fixed in version 2.6.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13251 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-13251?
- Check whether you run Perfmatters at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A directory traversal vulnerability exists in the Perfmatters plugin for WordPress due to insufficient validation of the 's' parameter within the Local Google Fonts feature. An unauthenticated attacker can exploit this by sending a specially crafted request to read sensitive files (such as wp-config.php) from the server's filesystem. Successful exploitation requires specific preconditions: the Local Google Fonts feature must be enabled (it is disabled by default), 'pretty permalinks' must be active, and RSS feed links must remain enabled in the plugin settings. The vulnerability was addressed in version 2.6.5 by adding domain verification and content type validation to the font downloading logic.
Affected products
- perfmatters Perfmatters up to, and including, 2.6.4
Timeline
- 2026-06-30: patched: Fixed in version 2.6.5
- 2026-07-02: disclosed: NVD publication date