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

CVE-2025-12550

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 jwsthemes OchaHouse ochahouse allows PHP Local File Inclusion.This issue affects OchaHouse: from n/a through <= 2.2.8.

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

Local File Inclusion (LFI) vulnerability in the jwsthemes OchaHouse WordPress theme allows attackers to include arbitrary PHP files from the server via unsanitized user input in include/require statements. This can expose sensitive files (like configuration files containing credentials) or potentially achieve code execution if attackers can upload files to accessible locations.

MitigationImplement strict input validation and use allowlists for any parameters used in include/require statements; avoid using user-supplied input directly in file inclusion functions, or disable PHP execution in upload directories.

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. Confirm OchaHouse theme is installed
    Navigate to wp-content/themes/ in your WordPress installation directory and verify the ochahouse or jwsthemes-ochahouse folder exists. Alternatively, check via WordPress admin under Appearance > Themes.
    Affected if The OchaHouse theme by jwsthemes is active or installed on the WordPress site
  2. Identify theme version
    Open the theme's style.css file (typically in wp-content/themes/ochahouse/style.css) and locate the Version: header in the comment block at the top. Compare this version number to any official changelog or release notes if available.
    Affected if The installed version matches or predates any vulnerable version range for this CVE
  3. Locate file inclusion code
    Search the theme directory for PHP files containing include, require, include_once, or require_once statements that use variables as the file path (e.g., include($var); or require($_GET['page']);). Use grep or manually review PHP files in the theme folder.
    Affected if The theme contains dynamic file inclusion using unsanitized user input (such as GET or POST parameters)
  4. Identify the vulnerable parameter
    Examine any PHP files using variable-based include/require statements. Note which user-supplied parameters (from $_GET, $_POST, $_REQUEST) are used directly in these functions without sanitization.
    Affected if A parameter used in include/require is controllable via URL or form input without validation
  5. Test for LFI exploitability
    Attempt a controlled test by submitting a benign file path via the identified parameter (e.g., ?param=../../../../../../../../etc/passwd or ?param=../wp-config.php) in a non-production environment to verify if file contents are returned.
    Affected if The application returns contents of files outside the intended directory, confirming unsanitized input is accepted

A site is affected if it runs the jwsthemes OchaHouse WordPress theme with dynamic file inclusion using unsanitized user input in include/require statements.

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

Implement strict input validation and use allowlists for any parameters used in include/require statements; avoid using user-supplied input directly in file inclusion functions, or disable PHP execution in upload directories.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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