dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-13251

HIGH · 7.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Perfmatters plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.6.4 via the 's' parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires the Local Google Fonts feature to be enabled (disabled by default), pretty permalinks to be active, and RSS feed links to remain enabled in the plugin settings.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Perfmatters WordPress plugin versions up to 2.6.4 contain a directory traversal vulnerability via the 's' parameter that allows unauthenticated attackers to read arbitrary files on the server. Successful exploitation requires three conditions: Local Google Fonts feature enabled, pretty permalinks active, and RSS feed links enabled in plugin settings.

MitigationUpdate to a patched version of Perfmatters when available; if unavailable, disable Local Google Fonts feature and RSS feed links in plugin settings as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Perfmatters plugin is installed
    Navigate to WordPress admin dashboard > Plugins and verify Perfmatters is listed as an active plugin. Alternatively, check for the /wp-content/plugins/perfmatters/ directory on the server.
    Affected if Perfmatters plugin is installed and active
  2. Determine installed Perfmatters version
    In WordPress admin, go to Plugins > Installed Plugins > Perfmatters and view the version number displayed. Alternatively, check the main plugin file for the 'Version' header comment.
    Affected if Version is 2.6.4 or lower (any version up to and including 2.6.4)
  3. Verify Local Google Fonts feature is enabled
    In WordPress admin, go to Perfmatters plugin settings. Look for the Local Google Fonts option (typically under Options or Fonts section) and confirm it is turned ON or enabled.
    Affected if Local Google Fonts setting is enabled
  4. Confirm pretty permalinks are active
    In WordPress admin, go to Settings > Permalinks and verify that a non-default permalink structure is selected (not 'Plain'). Common options include Day and name, Month and name, or Post name.
    Affected if Pretty permalinks are enabled with any custom URL structure
  5. Check if RSS feed links are enabled in Perfmatters
    In WordPress admin, navigate to Perfmatters plugin settings. Look for an RSS, Feed, or Extras section and verify if RSS feed link options are enabled or checked.
    Affected if RSS feed link settings are enabled in the plugin

All five conditions must be true for the vulnerability to be exploitable: Perfmatters version 2.6.4 or lower, Local Google Fonts enabled, pretty permalinks active, and RSS feed links enabled in plugin settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of Perfmatters when available; if unavailable, disable Local Google Fonts feature and RSS feed links in plugin settings as a compensating control.

Recommended fix Moderate confidence

Perfmatters 2.6.5 or later (check WordPress plugin repository for latest version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Perfmatters plugin
  4. 4. Check the current version number displayed under the plugin name
  5. 5. If the installed version is 2.6.4 or earlier, update the plugin to the latest available version
  6. 6. After updating, verify that the Local Google Fonts feature is still disabled (recommended) or ensure it is configured securely if enabled
  7. 7. Confirm pretty permalinks are active as required by the plugin
  8. 8. Verify the RSS feed links setting in plugin options based on site requirements
Caveat Check Perfmatters changelog for any breaking changes between your current version and the new version before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13251 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13251 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data