CVE-2026-27067
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Syarif Mobile App Editor mobile-app-editor allows Upload a Web Shell to a Web Server.This issue affects Mobile App Editor: from n/a through <= 1.3.1.
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 confidenceThe mobile-app-editor component has an unrestricted file upload vulnerability that permits attackers to upload arbitrary file types, including malicious web shells, directly to the web server. This can enable remote code execution and complete system compromise.
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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 mobile-app-editor component presenceSearch your codebase, application directories, or installed packages for the 'mobile-app-editor' component name. Check package.json, composer.json, or similar dependency manifests if applicable.Affected if The mobile-app-editor component is found in your environment and has file upload functionality enabled.
-
Determine mobile-app-editor versionLocate the version information for the mobile-app-editor component through your package manager (npm list, pip show, etc.) or check version files within the component directory.Affected if The installed version falls within any vulnerable version range for this CVE.
-
Verify file upload feature is enabledExamine the mobile-app-editor configuration files or source code for upload-related endpoints, functions, or settings that enable file upload capability.Affected if File upload functionality is enabled and accessible in the component.
-
Inspect file type validation logicReview the file upload handler code in mobile-app-editor to determine what file type validation exists. Look for allowlist/blocklist logic for file extensions and MIME types.Affected if There is no strict allowlist-based validation, or validation can be bypassed for file extensions like .php, .js, .asp, .exe, or other executable types.
-
Check upload directory placementLocate the configured or default upload directory for the mobile-app-editor. Verify whether it is inside or outside the webroot by examining configuration files or upload path settings.Affected if Uploads are stored within the webroot or a directory that permits script execution.
Your environment is affected if the mobile-app-editor component is present with file upload enabled, lacks strict allowlist-based file validation, and stores uploads in a web-accessible directory that allows script execution.
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 allowlist-based file validation (extension, MIME type, and content inspection), store uploads outside the webroot, and disable script execution in upload directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27067 — 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-27067 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