CVE-2026-22361
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 A-Mart a-mart allows PHP Local File Inclusion.This issue affects A-Mart: from n/a through <= 1.0.2.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the axiomthemes A-Mart WordPress theme (versions up to 1.0.2). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file path parameters to read sensitive local files from the server.
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.
-
Identify if A-Mart theme is installedCheck the WordPress themes directory at /wp-content/themes/ for a folder named 'a-mart', 'amart', or similar variant. In WordPress admin, go to Appearance > Themes to list installed themes.Affected if The A-Mart theme folder exists in the WordPress themes directory.
-
Determine the installed theme versionOpen the theme's style.css file (typically at /wp-content/themes/a-mart/style.css) and locate the 'Version:' header in the CSS comment block at the top of the file.Affected if The version listed is 1.0.2 or lower.
-
Inspect theme PHP files for dynamic file inclusionSearch all PHP files in the theme directory for include, require, include_once, or require_once statements that use variables (such as $_GET, $_POST, or $_REQUEST) without sanitization. Look for patterns like 'include($_GET["..."]' or 'require($var)', particularly in files handling template or file loading functionality.Affected if PHP files contain include/require statements using unsanitized user-supplied input from request parameters.
-
Test for LFI parameter handling (if discovered)If a vulnerable parameter is found (for example, a file= or template= parameter in the theme's PHP code), review whether the code uses basename() or realpath() to sanitize the input before passing it to include/require. Absence of such sanitization indicates the vulnerability is present.Affected if The code passes user-supplied filename parameters directly to include/require without basename() or realpath() validation.
You are affected if the A-Mart theme (version 1.0.2 or lower) is installed AND contains PHP files that use unsanitized request parameters in include/require statements.
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 dataImplement strict input validation using allowlists, sanitize file path parameters with basename() and realpath(), and avoid using user-supplied input directly in include/require statements.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22361 — 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-22361 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