CVE-2026-27343
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 VanKarWai Airtifact airtifact allows PHP Local File Inclusion.This issue affects Airtifact: from n/a through <= 1.2.91.
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 confidenceVanKarWai Airtifact up to version 1.2.91 contains a PHP Local File Inclusion (LFI) vulnerability caused by improper control of filename parameters in include/require statements. Attackers can manipulate file path inputs to include arbitrary files from the server filesystem, potentially exposing sensitive configuration files, credentials, or source 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify VanKarWai Airtifact installationSearch for files or directories named 'VanKarWai', 'Airtifact', or related application files in the web root or application directories. Check for PHP files containing references to 'VanKarWai' or 'Airtifact' in headers or comments.Affected if The application is present in the environment and is named VanKarWai Airtifact.
-
Determine the installed versionLocate version information in the application - check for version.php, about.php, README files, configuration files, or a changelog file within the application directory. Compare the found version against the affected range of up to 1.2.91.Affected if The installed version is 1.2.91 or any earlier version.
-
Locate PHP file inclusion functionsSearch the application source code for dynamic usage of include, require, include_once, require_once, or similar functions where the file path is not a hardcoded string. Look for patterns like include($_GET['...']) or require($var) in PHP files.Affected if Dynamic file inclusion functions are found where user input could control the file path.
-
Examine input sources for file inclusionTrace the variables passed to include/require statements back to their origin. Check if they receive input from $_GET, $_POST, $_REQUEST, or other user-controllable sources without proper sanitization.Affected if User-controllable parameters can reach file inclusion functions without validation.
-
Check for proper input validationReview the code handling file inclusion paths. Determine if there is allowlist validation, basename() usage with allowlist checking, or if the input is used directly in the include/require statement.Affected if File inclusion parameters accept arbitrary file paths without allowlist validation or sanitization.
The environment is affected if VanKarWai Airtifact version 1.2.91 or earlier is installed and contains PHP file inclusion code that accepts unsanitized user input to control which files are included.
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 an allowlist approach for all file inclusion operations. Replace dynamic file inclusion with hardcoded includes or use basename() with validated allowlist checking. Disable allow_url_include and restrict file system access permissions.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27343 — 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-27343 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