CVE-2026-27381
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 thembay Aora aora allows PHP Local File Inclusion.This issue affects Aora: from n/a through <= 1.3.15.
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 PHP Local File Inclusion (LFI) vulnerability in thembay Aora (version <= 1.3.15). The application improperly controls filenames used in include/require statements, allowing attackers to manipulate path parameters to include arbitrary local files from the server filesystem.
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 thembay Aora installationLocate the thembay Aora application on the server. Check for the presence of the main application directory (commonly named 'aora', 'thembay-aora', or similar) and identify its root path.Affected if The thembay Aora application is installed on the server.
-
Determine installed versionCheck the version file, composer.json, or any version identifier within the thembay Aora installation. Common locations include a 'version' file in the root directory, a 'composer.json' file, or the admin panel version display.Affected if The installed version is 1.3.15 or any version lower than 1.3.15.
-
Identify PHP files using include or requireSearch the application source code for PHP files that contain include, require, include_once, or require_once statements. Examine these files for any dynamic path construction.Affected if The application contains PHP files using include/require statements.
-
Check for user input in file inclusion pathsExamine the PHP files identified in step 3. Look for $_GET, $_POST, $_REQUEST, or other user-supplied variables being used directly within include, require, include_once, or require_once statements without proper sanitization or validation.Affected if User-supplied input (from GET, POST, or REQUEST parameters) flows directly into include/require statements without validation.
-
Identify the vulnerable parameterTrace the user input found in step 4 to determine which HTTP parameter controls the file inclusion. Check if this parameter can be manipulated through HTTP requests to specify arbitrary file paths.Affected if A URL parameter (such as 'page', 'file', 'path', 'template', or similar) can be controlled by an attacker to influence the file included by the application.
You are affected if thembay Aora version 1.3.15 or lower is installed AND the application uses include/require statements with unvalidated user-controlled parameters that can be manipulated to access arbitrary local 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 dataImplement strict input validation using an allowlist approach for any parameters used in include/require statements, and avoid using user-supplied input directly in file inclusion paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27381 — 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-27381 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