dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-13088

HIGH · 8.8 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Category and Product Woocommerce Tabs plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.0. This is due to insufficient input validation on the 'template' parameter in the categoryProductTab() function. This makes it possible for authenticated attackers, with contributor level access and above, to include and execute arbitrary .php files on the server.

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 Category and Product Woocommerce Tabs WordPress plugin versions up to 1.0 contains a Local File Inclusion vulnerability in the categoryProductTab() function. The 'template' parameter is not properly validated, allowing authenticated users with contributor-level access or higher to include and execute arbitrary PHP files on the server by manipulating the parameter to point to existing .php files.

MitigationImmediately disable or remove the plugin since no patched version is available; if the functionality is required, implement proper input validation using allowlist approach or realpath() checks on the template parameter before including files, or migrate to an alternative plugin.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named similar to 'category-and-product-woocommerce-tabs' or containing 'woocommerce-tabs'. List all installed plugins and look for this specific plugin.
    Affected if The plugin directory exists in wp-content/plugins/ and contains the Category and Product Woocommerce Tabs plugin files.
  2. Determine the installed version
    Open the main plugin PHP file (typically the first .php file in the plugin folder) and look for the plugin header comment containing 'Version:' or check the readme.txt file for the version number.
    Affected if The version number found is 1.0 or lower (all versions up to and including 1.0 are affected).
  3. Confirm authentication requirements
    In the WordPress admin dashboard, navigate to Users > All Users and review the roles assigned. Check if any users have the 'Contributor' role or higher (Editor, Author, Administrator).
    Affected if There are one or more user accounts with Contributor-level access or higher who could potentially trigger the vulnerable function.
  4. Identify the vulnerable function location
    Examine the plugin source code for the categoryProductTab() function. The function should accept a 'template' parameter without proper sanitization. Look for include(), require(), or similar file inclusion statements using this parameter.
    Affected if The categoryProductTab() function exists in the plugin and processes a 'template' parameter through a file inclusion function without validated input.

You are affected if the Category and Product Woocommerce Tabs plugin is installed at version 1.0 or lower AND at least one user with Contributor-level access or higher exists on the WordPress site.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately disable or remove the plugin since no patched version is available; if the functionality is required, implement proper input validation using allowlist approach or realpath() checks on the template parameter before including files, or migrate to an alternative plugin.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13088 — 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-2025-13088 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