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

CVE-2026-57805

HIGH · 7.5 CVSS v3.1 Published 2026-07-13
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 5 weeks old

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 Select-Themes Tonda tonda allows PHP Local File Inclusion.This issue affects Tonda: from n/a through <= 2.5.

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

A PHP Local File Inclusion (LFI) vulnerability exists in the Tonda theme (versions <=2.5) by Select-Themes. The vulnerability stems from improper control of filenames used in include/require statements, allowing attackers to manipulate file paths and potentially execute arbitrary PHP code by including malicious files from the local filesystem.

MitigationUpgrade the Tonda theme to the latest version, or implement strict input validation/sanitization on all file inclusion parameters (include, require, include_once, require_once) to restrict paths to whitelisted directories. If upgrading is not immediately possible, disable the affected functionality or implement Web Application Firewall (WAF) rules as a temporary mitigation.

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. Locate the Tonda theme installation
    Search the webroot for directories named 'tonda', 'select-tonda', or similar. Common paths include wp-content/themes/tonda (WordPress) or themes/tonda (generic). Check theme style.css or theme.json for the version declaration.
    Affected if The Tonda theme by Select-Themes is installed and the version cannot be determined or is <=2.5
  2. Verify the installed theme version
    Open the theme's main style.css file (usually in the theme root) and look for 'Version:' in the header comment. Compare this version number against the <=2.5 threshold.
    Affected if The declared version is 2.5 or lower, or the version line is missing/unreadable
  3. Identify PHP files with include/require statements
    Search the theme directory for .php files containing 'include', 'require', 'include_once', or 'require_once' - especially those using variables in the path (e.g., include($file), require($_GET['page']).
    Affected if Dynamic file inclusion statements that use variable or user-input-derived paths are found in the theme's PHP files
  4. Check for unsafe parameter handling in file inclusion
    Examine the identified include/require statements for lack of sanitization. Look for direct use of $_GET, $_POST, or $_REQUEST variables in the file path without basename(), realpath(), or whitelist validation.
    Affected if User-controllable parameters (from URL or form input) flow directly into include/require statements without validation
  5. Identify accessible vulnerable endpoints
    If the above conditions exist, test common parameter names like 'page', 'file', 'template', 'path', or 'include' in the theme's PHP files to see if they can be manipulated via HTTP requests.
    Affected if The vulnerable file inclusion code is reachable via HTTP requests and accepts user-supplied path values

If the Tonda theme version is 2.5 or lower AND the theme contains dynamic include/require statements that accept user input without sanitization, the environment is affected by this LFI vulnerability.

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

Upgrade the Tonda theme to the latest version, or implement strict input validation/sanitization on all file inclusion parameters (include, require, include_once, require_once) to restrict paths to whitelisted directories. If upgrading is not immediately possible, disable the affected functionality or implement Web Application Firewall (WAF) rules as a temporary mitigation.

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-2026-57805 — 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-2026-57805 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