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

CVE-2026-22513

HIGH · 8.1 CVSS v3.1 Published 2026-03-25
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 Triompher triompher allows PHP Local File Inclusion.This issue affects Triompher: from n/a through <= 1.1.0.

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 AncoraThemes Triompher theme (version 1.1.0 and below). The vulnerability stems from improper control of filenames used in PHP include/require statements, allowing attackers to manipulate file paths and potentially execute arbitrary PHP code or access sensitive files on the server.

MitigationFix the file inclusion vulnerability by removing or properly validating user-supplied input before using it in include/require statements. Implement allowlist-based validation, use basename() and realpath() to sanitize paths, and ensure user input cannot traverse outside the intended directory.

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 Triompher theme installation
    Locate the theme directory - typically at wp-content/themes/triompher for WordPress, or /themes/triompher for other PHP applications. Check for the existence of theme configuration files like style.css or theme.json in that directory.
    Affected if The Triompher theme by AncoraThemes is installed on the server
  2. Identify PHP file inclusion patterns
    Search the theme's PHP files (particularly header.php, footer.php, functions.php, and page templates) for dynamic include/require statements. Look for patterns like 'include($_GET[...])', 'require($_REQUEST[...])', or similar constructs where user-supplied parameters are used directly in file inclusion functions.
    Affected if The theme code contains include/require statements that use $_GET, $_POST, $_REQUEST, or similar superglobals without input validation
  3. Locate the vulnerable parameter
    Examine the identified include/require code to find which parameter name is being used (common names include 'page', 'file', 'template', 'view', 'include', or 'load'). Verify whether the parameter value is sanitized before being used in the include/require statement.
    Affected if A user-controllable parameter is passed directly to include/require without validation like basename(), realpath(), or allowlist checks
  4. Test for path traversal capability
    If the vulnerable parameter is identified, attempt to access known file paths via HTTP request (e.g., ?page=../../../../etc/passwd or ?file=../../windows/system32/drivers/etc/hosts). Compare the response to confirm if arbitrary local files can be read.
    Affected if The parameter accepts path traversal sequences (..) and returns file contents from outside the theme directory
  5. Review PHP configuration
    Check the PHP configuration file (php.ini) for the allow_url_include directive. This can be inspected via phpinfo() or by checking the server configuration.
    Affected if allow_url_include is enabled (this increases severity but is not required for basic LFI)

A server is affected if the AncoraThemes Triompher theme is installed AND contains PHP code that uses user-supplied input directly in include/require statements without validation, allowing arbitrary file reads.

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

Fix the file inclusion vulnerability by removing or properly validating user-supplied input before using it in include/require statements. Implement allowlist-based validation, use basename() and realpath() to sanitize paths, and ensure user input cannot traverse outside the intended directory.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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