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

CVE-2025-67526

HIGH · 7.5 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThimPress Sailing sailing allows PHP Local File Inclusion.This issue affects Sailing: from n/a through < 4.4.6.

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

Local File Inclusion (LFI) vulnerability in the ThimPress Sailing WordPress plugin allows attackers to include arbitrary files from the server via improper input validation in PHP include/require statements. The vulnerability affects versions prior to 4.4.6 and could enable reading sensitive local files.

MitigationUpdate Sailing plugin to version 4.4.6 or later. Review and sanitize any custom code that handles file inclusion operations to ensure user-supplied input is never used in include/require statements without strict validation.

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

CVSS:3.1/AV:N/AC:H/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. Check installed Sailing plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, find 'Sailing' (by ThimPress), and note the version number displayed. Alternatively, inspect the plugin's main PHP file (typically sailing.php or similar in wp-content/plugins/thim-sailing/) and look for the 'Version:' field in the plugin header comment.
    Affected if The displayed version is lower than 4.4.6 (e.g., 4.4.5, 4.4.0, or any version before 4.4.6)
  2. Locate plugin file inclusion code
    Using a file manager or grep tool, search within the thim-sailing plugin directory (wp-content/plugins/thim-sailing/) for PHP include, include_once, require, or require_once statements that use variables as file paths without sanitization. Examine files in the plugin's inc/, includes/, or core/ directories where such patterns are commonly found.
    Affected if You find include/require statements using unsanitized user input (e.g., include($_GET['file']); or require($theme_dir . $_POST['template']);) without proper validation functions like sanitize_file_name() or realpath() checks
  3. Identify the vulnerable parameter endpoint
    Review the plugin's PHP files for parameters passed via GET or POST requests that control file inclusion paths. Look for patterns like $_GET['template'], $_GET['file'], $_REQUEST['path'], or similar that are used directly in include/require statements. Check AJAX handlers (admin-ajax.php) and any custom endpoint files.
    Affected if A parameter (such as 'file', 'template', 'path', or similar) is directly used in include/require without validation, and that endpoint is publicly accessible
  4. Verify if custom file inclusion templates exist
    Check the theme or child theme directories for custom template files that may have been created for the Sailing plugin. Look in wp-content/themes/ and subdirectories for PHP files that contain include/require logic referencing plugin variables. Inspect any custom hooks or overrides added to theme's functions.php.
    Affected if Custom template files or overrides exist that use plugin-related variables in include/require without sanitization, extending the vulnerability surface beyond the core plugin

You are affected if the Sailing plugin version is below 4.4.6 AND the plugin's file inclusion code with unsanitized input is present and accessible on your 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.

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

Update Sailing plugin to version 4.4.6 or later. Review and sanitize any custom code that handles file inclusion operations to ensure user-supplied input is never used in include/require statements without strict validation.

Recommended fix High confidence

Sailing version 4.4.6 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins page.
  3. 3. Find the 'Sailing' theme/plugin by ThimPress.
  4. 4. Update the Sailing theme/plugin to version 4.4.6 or later.
  5. 5. Verify the update was successful by checking the version number in the theme/plugin details.
  6. 6. Test that the site functionality remains intact after the update.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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