dbcve.org
CatamaranWordPress extension · Axiomthemes

CVE-2025-58936

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 1.15 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in axiomthemes Catamaran catamaran allows PHP Local File Inclusion.This issue affects Catamaran: from n/a through <= 1.15.

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 · moderate confidence

The Catamaran WordPress theme by axiomthemes contains a Local File Inclusion (LFI) vulnerability (CWE-22) that allows attackers to manipulate filename parameters in PHP include/require statements to access sensitive local files. This can potentially lead to remote code execution if attackers can upload files or access system files.

MitigationUpdate to a patched version of the Catamaran theme when available; otherwise, audit and sanitize all include/require statements to validate and restrict file paths, implement allowlists for permitted files, and avoid using user-supplied input directly in file inclusion functions.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CatamaranWordPress extension
Affected:<= 1.15

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify if Catamaran theme is installed
    In WordPress admin dashboard, go to Appearance > Themes. Look for the Catamaran theme by axiomthemes in the installed themes list.
    Affected if Catamaran theme by axiomthemes is present in the WordPress installation
  2. Determine the installed theme version
    In WordPress admin, click on the Catamaran theme details. Note the version number displayed. Alternatively, check the style.css file in wp-content/themes/catamaran/ for the 'Version:' header.
    Affected if Version is 1.15 or lower
  3. Search for vulnerable file inclusion patterns
    Review PHP files in the theme directory (wp-content/themes/catamaran/) for include, require, include_once, or require_once statements that use variables in the path without validation. Look for patterns like 'include($_GET[...])' or 'require($filename)' where the variable could be manipulated.
    Affected if Any PHP file in the theme uses user-supplied input directly in include/require statements without sanitization
  4. Check for exposure of file path parameters
    Test the theme's frontend and admin URLs with parameter variations (e.g., ?template=, ?file=, ?page=) that might be passed to inclusion functions. Review the theme's PHP code to identify all request parameters that flow into file inclusion functions.
    Affected if URL parameters can be manipulated to reference arbitrary files outside the intended theme directory
  5. Audit theme configuration files
    Examine the theme's main PHP files (such as functions.php, header.php, footer.php, or any template-loader files) for dynamic file includes. Look for extract(), parse_str(), or similar functions that populate variables from request input.
    Affected if Dynamic file inclusion code exists that uses unsanitized input from HTTP requests

The environment is affected if the Catamaran theme version is 1.15 or lower and the theme contains file inclusion code that uses user-supplied input without validation.

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
Upgrade available Upgrade to a release after 1.15
Interim mitigation

Update to a patched version of the Catamaran theme when available; otherwise, audit and sanitize all include/require statements to validate and restrict file paths, implement allowlists for permitted files, and avoid using user-supplied input directly in file inclusion functions.

Fix this in Catamaran Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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