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

CVE-2025-49261

HIGH · 8.1 CVSS v3.1 Published 2025-06-17
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 thembay Diza diza allows PHP Local File Inclusion.This issue affects Diza: from n/a through <= 1.3.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

This is a PHP Local File Inclusion (LFI) vulnerability in the thembay Diza theme where user-supplied input is not properly validated before being used in include/require statements. An attacker could manipulate file path parameters to read sensitive local files (like /etc/passwd, configuration files) or potentially execute arbitrary PHP code if they can upload files to the server.

MitigationImplement strict input validation on all file inclusion parameters using a whitelist approach, sanitize or strip directory traversal characters (..), and avoid using user input directly in include/require statements. Consider using a whitelist of allowed files/pages.

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 thembay Diza theme is installed
    Search your web application codebase for files belonging to the Diza theme, typically found in wp-content/themes/diza/ (for WordPress) or similar theme directories. Check theme metadata files like style.css or theme.json for the theme name.
    Affected if The thembay Diza theme is present in the application codebase.
  2. Identify PHP files using include/require with dynamic input
    Search theme files for include, include_once, require, or require_once statements where variables are passed as the path argument, such as include($file), include($_GET['page']), or require_once($path). Use grep or IDE search across theme PHP files.
    Affected if Dynamic file inclusion functions are used with variables that could be user-controlled.
  3. Inspect file path parameters in HTTP requests
    Review the application's URL parameters, POST data, or cookies that might supply file paths to include statements. Common parameter names include file, page, path, template, lang, or similar. Test these parameters with a benign path like /etc/passwd.
    Affected if User-supplied parameters are directly used in include/require without validation.
  4. Check for directory traversal filtering
    Examine the code handling file inclusion for the presence of directory traversal sequences (..) or null byte injection. Verify if the code strips, validates, or rejects sequences like ../ or uses basename() or realpath() for sanitization.
    Affected if No sanitization or whitelist validation exists for path traversal characters.
  5. Verify file access restrictions
    Check if included files are restricted to a specific allowed directory or whitelist of files. Look for checks that verify the file exists within a permitted base path before inclusion.
    Affected if User input can reach include statements without path restrictions or whitelist validation.

A user is affected if the thembay Diza theme is installed AND user-controlled input flows directly into PHP include/require statements without validation, allowing directory traversal or arbitrary file reading.

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 on all file inclusion parameters using a whitelist approach, sanitize or strip directory traversal characters (..), and avoid using user input directly in include/require statements. Consider using a whitelist of allowed files/pages.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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