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

CVE-2026-57788

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 Edge-Themes Aalto aalto allows PHP Local File Inclusion.This issue affects Aalto: from n/a through <= 1.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 Edge-Themes Aalto theme allows attackers to include arbitrary local PHP files through unsanitized user input in include/require statements. This can enable unauthorized reading of sensitive system files and potentially lead to remote code execution if attacker-controlled files can be uploaded or accessed.

MitigationImplement strict input validation using whitelist approach for file paths, avoid using user input directly in include/require statements, and upgrade to a patched version if available.

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. Identify if Aalto theme is installed
    Locate the theme files - look for a folder named 'aalto' or 'Aalto' within your themes directory, typically in wp-content/themes/ (WordPress) or similar theme folder structure for the respective CMS. Check theme documentation or theme header files (style.css, theme.json) for the theme name.
    Affected if The Aalto theme by Edge-Themes is present in the environment
  2. Determine the installed theme version
    Open the theme's main style.css file or theme.json and locate the 'Version' field. Compare this version number against any documented affected version ranges if available from the theme's release notes or changelog.
    Affected if The version cannot be verified as unaffected or is within an affected range
  3. Locate include/require statements using user input
    Search the theme's PHP files for patterns like 'include($_GET[', 'require($_POST[', 'include($_REQUEST[', or similar direct usage of superglobal arrays in include/require statements. Use grep or a code editor to search for '$_GET', '$_POST', '$_REQUEST' combined with 'include' or 'require'.
    Affected if Files contain include/require statements that directly use unsanitized superglobal variables
  4. Inspect the vulnerable parameter handling
    For each identified vulnerable include/require statement, examine the surrounding code to confirm user input is passed without sanitization functions like basename(), realpath(), or whitelist validation.
    Affected if User input in include/require statements is not sanitized through validation functions before use
  5. Test for LFI via HTTP requests
    If the vulnerable parameter is identifiable (e.g., a 'page' or 'file' GET parameter), attempt to include a known safe file like /etc/passwd or a common log file to confirm the LFI exists. Only perform this test with authorization.
    Affected if Arbitrary local files can be included and their contents revealed through HTTP requests

If the Aalto theme is installed and contains include/require statements using unsanitized user input, 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

Implement strict input validation using whitelist approach for file paths, avoid using user input directly in include/require statements, and upgrade to a patched version if available.

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