CVE-2025-10465
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 Birtech Information Technologies Industry and Trade Ltd. Co. Sensaway allows Upload a Web Shell to a Web Server. This issue affects Sensaway: through 09022026. NOTE: Because the product was developed using outdated technology, the manufacturer is unable to fix the relevant vulnerabilities. Users of the Sensaway application are advised to contact the manufacturer and review updated products developed with newer technology.
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 confidenceSensaway application has an unrestricted file upload vulnerability (CWE-434) allowing attackers to upload malicious web shells to the web server. This enables remote code execution since the uploaded files can be executed by the web 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Confirm Sensaway application presenceLocate Sensaway installation directory or running service. Check for sensaway binary, web application files, or service process on the system.Affected if Sensaway application is installed and running
-
Identify Sensaway versionCheck application version via binary metadata, web interface version page, or configuration files in the installation directory.Affected if Version matches or falls within an affected range (if later clarified by vendor)
-
Verify file upload endpoint existsIdentify if web upload functionality is accessible. Check for upload forms, API endpoints, or administrative interfaces that accept file submissions.Affected if File upload functionality is exposed and accessible to the attacker
-
Check web server execution configurationInspect web server configuration (IIS, Apache, Nginx) for the upload directory. Verify if executable file types (.asp, .php, .jsp, .exe, .sh) can be executed from the upload location.Affected if Uploaded files are stored in a web-accessible directory and the web server can execute them
-
Review allowed file type restrictionsExamine application configuration or code for file type validation. Check if validation can be bypassed or if executable extensions are blocked.Affected if No server-side validation or weak validation allows uploading of executable file types
The environment is affected if Sensaway is running with accessible file upload functionality where uploaded files can be executed by the web server, enabling remote code 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 dataNo vendor patch available; contact manufacturer for updated product. Implement compensating controls such as WAF rules filtering executable file types, network-level file upload restrictions, or migrate to a supported product.
- Consultation8.0 h
- Implementation24.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 $12,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10465 — 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-2025-10465 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