CVE-2026-1358
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 · uneditedAirleader Master versions 6.381 and prior allow for file uploads without restriction to multiple webpages running maximum privileges. This could allow an unauthenticated user to potentially obtain remote code execution on the server.
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 confidenceAirleader Master versions 6.381 and prior contains an unrestricted file upload vulnerability across multiple webpages. Unauthenticated attackers can upload arbitrary files (such as malicious scripts) to the server, which executes with maximum privileges due to the application running with elevated rights, enabling complete remote code execution.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Determine installed Airleader Master versionLocate the version information in the application administrative interface, about page, or check version files in the installation directory. Compare against the affected range: versions 6.381 and prior are vulnerable.Affected if The installed version is 6.381 or lower.
-
Identify accessible file upload endpointsReview the web application for pages that accept file uploads. Check if these pages are reachable without authentication.Affected if File upload functionality exists and is accessible to unauthenticated users.
-
Verify upload directory locationIdentify where uploaded files are stored. Check if the upload directory is located within the web server's document root (webroot).Affected if Uploaded files are stored inside the webroot, making them accessible via HTTP/HTTPS.
-
Check script execution permissions on upload directoryInspect web server configuration to determine whether script execution (e.g., PHP, ASP, JSP) is permitted in the upload directory.Affected if Script execution is allowed in the directory where uploads are stored, enabling uploaded files to be executed.
-
Assess web service privilege levelReview the user account or service identity under which the web server process runs. Determine if it runs with administrative or elevated privileges.Affected if The web service executes with maximum privileges, allowing uploaded malicious code to run with elevated access.
You are affected if your Airleader Master version is 6.381 or prior AND unauthenticated file upload pages are accessible AND uploaded files can be executed from the webroot.
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 file upload controls including file type allowlisting, MIME type validation, renaming uploaded files, storing uploads outside the webroot, disabling script execution in upload directories, and enforcing authentication on all upload endpoints.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1358 — 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-1358 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