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

CVE-2025-14359

HIGH · 8.1 CVSS v3.1 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 brandexponents Oshine allows PHP Local File Inclusion. This issue affects Oshine: from n/a before 7.3.0.

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 Oshine theme (brandexponents) before version 7.3.0 contains a PHP Local File Inclusion (LFI) vulnerability (CWE-98). This occurs when the application uses user-supplied input in include/require statements without proper validation, allowing attackers to include arbitrary PHP files from the server filesystem. This can potentially lead to remote code execution if the attacker can chain it with other vulnerabilities or upload malicious files.

MitigationUpgrade Oshine to version 7.3.0 or later. If patching is not immediately possible, implement strict whitelist-based validation on all file inclusion parameters and disable allow_url_include in PHP configuration.

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
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. Locate Oshine theme installation
    Check the wp-content/themes directory for the 'oshine' or 'oshine-master' folder. In WordPress admin, navigate to Appearance > Themes to confirm Oshine is active or installed.
    Affected if The Oshine theme folder exists in the WordPress themes directory.
  2. Identify installed Oshine version
    Open the style.css file within the Oshine theme folder and locate the 'Version:' header in the file comments. Alternatively, check the theme's main PHP file for a version constant or check the changelog file.
    Affected if The reported version number is lower than 7.3.0 (e.g., 7.2.x, 7.1.x, 7.0.x, etc.) or no version is specified.
  3. Inspect file inclusion functionality
    Search the theme's PHP files for include, require, include_once, or require_once statements that use variables in the file path (e.g., include($file), require($_GET['path'])). Look for parameters that might accept file paths in URL requests.
    Affected if The theme contains dynamic file inclusion code that uses user-controlled input without proper sanitization.
  4. Test for accessible file inclusion parameters
    If identifiable, attempt a benign test request to the suspected endpoint with a manipulated file path parameter (e.g., ?file=../../wp-config.php). Check if the application returns file contents or error messages revealing path traversal.
    Affected if The application accepts and processes file path parameters without validation, allowing directory traversal.

A user is affected if the Oshine theme version is below 7.3.0 and the vulnerable file inclusion functionality is accessible and exploitable.

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

Upgrade Oshine to version 7.3.0 or later. If patching is not immediately possible, implement strict whitelist-based validation on all file inclusion parameters and disable allow_url_include in PHP configuration.

Recommended fix Moderate confidence

Oshine 7.3.0 or later

  1. Check current installed version of Oshine theme in WordPress admin under Appearance > Themes
  2. Download Oshine version 7.3.0 or later from the official source (ThemeForest or Brand Exponents website)
  3. Backup the current WordPress site including database and files
  4. Deactivate the current Oshine theme
  5. Upload and install the new Oshine 7.3.0+ version via WordPress admin or via FTP
  6. Reactivate the Oshine theme
  7. Verify the site functionality and appearance work correctly after upgrade
  8. Check theme settings and reapply any custom configurations if needed
Caveat Review changelog for any deprecated features or settings changes between your current version and 7.3.0; test in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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