CVE-2026-22370
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in axiomthemes Marveland marveland allows PHP Local File Inclusion.This issue affects Marveland: from n/a through <= 1.3.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 · high confidenceThe Marveland theme by axiomthemes contains a PHP Local File Inclusion (LFI) vulnerability where user-controlled input is used in include/require statements without proper validation. Attackers can manipulate the input to include arbitrary local PHP files, potentially exposing sensitive system files or executing malicious code.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Marveland theme installationCheck your web server's wp-content/themes/ directory for a folder named 'marveland' or similar. Verify the theme is active in WordPress admin under Appearance > Themes.Affected if The Marveland theme by axiomthemes is installed and active on the WordPress site.
-
Identify vulnerable include/require patternsSearch the theme PHP files for dynamic include(), require(), include_once(), or require_once() statements that use variables or request parameters without sanitization. Look for patterns like 'include($_GET["..."])' or 'require($var)'.Affected if The theme contains include/require statements that incorporate user input (GET, POST, or COOKIE parameters) directly into file paths without validation.
-
Check the specific vulnerable parameterExamine the identified include/require code to determine which parameter controls the file inclusion. Common parameter names include 'page', 'file', 'template', 'include', or 'path'.Affected if A parameter controllable by the user (via URL or form input) is used in the inclusion logic without allowlist validation or sanitization.
-
Verify the vulnerability is exploitableTest accessing the site with a modified parameter value pointing to a known PHP file, such as '?param=../../wp-config.php' or similar path traversal sequences, observing if the file content is displayed or executed.Affected if The include/require statement processes path traversal sequences and allows arbitrary local file inclusion.
A site is affected if the Marveland theme is installed and contains dynamic include/require statements that use unsanitized user input to load PHP files.
Generated from the published advisory. Verify against your own configuration.
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 dataSanitize and validate all user input used in include/require statements, implement an allowlist of permitted files, or refactor to use a switch/case structure instead of dynamic file inclusion.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22370 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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