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

CVE-2026-22515

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 VegaDays vegadays allows PHP Local File Inclusion.This issue affects VegaDays: from n/a through <= 1.2.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

Local File Inclusion vulnerability in the VegaDays PHP theme allows attackers to manipulate file include statements to execute arbitrary PHP code from local files on the server, potentially leading to full system compromise.

MitigationImplement strict input validation and whitelisting for file include paths, disable allow_url_include, and upgrade to a patched version when available. Review and restrict file access permissions.

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. Identify if VegaDays PHP theme is installed
    Search the web server's themes or templates directory for a folder named 'vegadays' or files containing 'vegadays' in the filename. Common paths include /wp-content/themes/ (WordPress), /themes/ (other CMS), or the application's theme directory.
    Affected if The VegaDays theme folder or files are present on the server
  2. Determine the installed VegaDays version
    Check the theme's style.css, header.php, or a dedicated version file (often theme.json, info.xml, or theme.php) for a version number. Search for 'Version:' comment or '$theme_version' variable definition.
    Affected if A version number exists but no patched version is confirmed, or the version cannot be determined
  3. Verify PHP file inclusion functions are reachable
    Examine the theme's PHP files for include, require, include_once, or require_once statements that use variables or user-controlled input in the path (e.g., include($_GET['page']). Search for patterns like 'include($', 'require($_', or dynamic includes.
    Affected if Dynamic file inclusion using unsanitized variables is found in the theme's PHP files
  4. Check PHP configuration for dangerous settings
    Review php.ini or check PHP settings via phpinfo() for allow_url_include=1 and register_globals=1 (if older PHP). Also check if open_basedir restrictions are not configured.
    Affected if allow_url_include is enabled or open_basedir is not restricting file access to the web directory
  5. Identify exposed entry points
    Test whether the vulnerable file inclusion parameters are accessible via HTTP requests. Look for URL patterns in the theme that pass file paths as GET or POST parameters (e.g., ?file=, ?page=, ?template=).
    Affected if URL parameters accepting file paths are accessible without authentication and can be manipulated to include local files
  6. Audit file permissions on the web directory
    Review file system permissions on the web root and subdirectories. Check if uploaded files or writable directories exist that could be used to place malicious PHP files for inclusion.
    Affected if The web directory contains writable folders or allows file uploads that an attacker could leverage to place executable PHP files

The environment is affected if the VegaDays PHP theme is installed and contains dynamic file inclusion code that accepts user input, regardless of specific version, especially if PHP configuration allows broad file access.

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 and whitelisting for file include paths, disable allow_url_include, and upgrade to a patched version when available. Review and restrict file access permissions.

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