CVE-2025-1165
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 · uneditedA vulnerability, which was classified as critical, was found in Lumsoft ERP 8. Affected is the function DoUpload/DoWebUpload of the file /Api/FileUploadApi.ashx. The manipulation of the argument file leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.
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 confidenceLumsoft ERP 8 contains an unrestricted file upload vulnerability in the DoUpload/DoWebUpload functions of /Api/FileUploadApi.ashx. The application fails to properly validate uploaded files, allowing attackers to upload malicious files (such as web shells) to the server. This can lead to remote code execution if the uploaded files are accessible via 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 Lumsoft ERP 8 installationInspect HTTP responses from the application, check for 'Lumsoft' or 'ERP' strings in headers/pages, or query the application for its version informationAffected if The application is running Lumsoft ERP version 8.x
-
Check if FileUploadApi.ashx endpoint existsAttempt to access /Api/FileUploadApi.ashx via HTTP request and observe the responseAffected if The endpoint returns a valid response (not 404) indicating the upload API is present
-
Verify upload functionality is enabledReview application configuration files for upload-enabled modules, or attempt a test upload request to the DoUpload/DoWebUpload functionsAffected if The upload functions accept requests and return success responses rather than rejecting them
-
Inspect upload directory locationCheck web server configuration for the path where uploaded files are stored, typically in application configuration or by examining uploaded file URLsAffected if Upload directory is within the web root (accessible via HTTP) rather than stored outside the web directory
-
Check for file validation controlsReview application configuration or attempt to upload a file with a potentially dangerous extension (.asp, .php, .aspx, .exe)Affected if The application accepts files without extension/MIME type validation or allows executable extensions
A user is affected if they run Lumsoft ERP 8 with the FileUploadApi.ashx endpoint accessible and uploads stored within the web root without proper file validation.
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 validation including extension allowlists, MIME type verification, magic byte/content validation, and store uploads outside the web root with random filenames. Restrict execution permissions on the upload directory.
- 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-2025-1165 — 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-1165 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