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

CVE-2025-49366

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
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 AncoraThemes Hanani hanani allows PHP Local File Inclusion.This issue affects Hanani: from n/a through <= 1.2.11.

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 Hanani theme <= 1.2.11 contains a PHP Local File Inclusion (LFI) vulnerability where improper control of filenames in include/require statements allows attackers to include arbitrary local PHP files, potentially leading to remote code execution.

MitigationUpgrade to a patched version of Hanani; if no patch exists, implement strict input validation on all include/require parameters using whitelist validation or basename() functions to prevent path traversal.

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. Check Hanani theme version
    Locate the theme's style.css file (typically in /wp-content/themes/hanani/) and find the 'Version:' declaration in the file header. Alternatively, check the theme version via WordPress admin appearance section.
    Affected if The version number is 1.2.11 or lower.
  2. Identify include/require usage in theme
    Search all PHP files in the theme directory for 'include' and 'require' statements (including include_once, require_once). Use grep or a code search tool: grep -r "include(" /path/to/wp-content/themes/hanani/
    Affected if The theme contains dynamic include/require statements that use variables without sanitization.
  3. Examine include/require parameters for user input
    For each include/require statement found, inspect whether the parameter is a variable (e.g., include($file); include($_GET['page']);). Trace whether that variable can be controlled via HTTP request parameters.
    Affected if Parameters to include/require accept raw user input (e.g., $_GET, $_POST, $_COOKIE) without validation.
  4. Check for path traversal vulnerability
    Look for patterns like '../' in sanitization logic, or absence of basename(), realpath(), or whitelist checks around the include/require parameter. Attempt to determine if requests like ?file=../../wp-config can reach the include statement.
    Affected if No basename(), realpath(), or whitelist validation is applied before the include/require statement executes.
  5. Verify vulnerable code is web-accessible
    Confirm the file containing the vulnerable include/require is accessible via web request (not restricted by .htaccess or authentication). Test if the parameter can be manipulated through HTTP GET or POST parameters.
    Affected if The vulnerable include/require code is reachable via HTTP requests and accepts external input.

You are affected if Hanani theme version is 1.2.11 or lower AND the theme contains include/require statements that accept unsanitized user input, allowing path traversal to execute arbitrary local PHP files.

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 to a patched version of Hanani; if no patch exists, implement strict input validation on all include/require parameters using whitelist validation or basename() functions to prevent path traversal.

Recommended fix Moderate confidence

Latest available version of Hanani theme after 1.2.11 (contact vendor for specific version number)

  1. 1. Identify the current installed version of the Hanani theme by AncoraThemes
  2. 2. Check AncoraThemes official repository or changelog for version releases after 1.2.11
  3. 3. Download and apply the latest available version of Hanani theme (version > 1.2.11)
  4. 4. Verify the upgrade was successful by checking the theme version
  5. 5. Test the application to confirm the file inclusion vulnerability is remediated
Caveat Review theme changelog for any breaking changes between current version and new version before upgrading

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

Have this fixed 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 help mitigating

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-49366 — 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-49366 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