CVE-2025-41347
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 · uneditedUnlimited upload vulnerability for dangerous file types in WinPlus v24.11.27 from Informática del Este. This vulnerability allows an attacker to upload a 'webshell' by sending a POST request to '/WinplusPortal/ws/sWinplus.svc/json/uploadfile'.
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 confidenceWinPlus v24.11.27 contains an unrestricted file upload vulnerability at the /WinplusPortal/ws/sWinplus.svc/json/uploadfile endpoint. The application fails to validate uploaded file types, allowing attackers to upload dangerous executable files such as webshells via POST requests. This can lead to remote code execution on the affected server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 24.11.27CVSS 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.
-
Identify installed WinPlus versionCheck the application version displayed in the WinPlus portal interface, or query the application binaries/config files for version information. Common locations include the about page, config files, or service information.Affected if The installed version is exactly 24.11.27.
-
Verify the vulnerable endpoint existsCheck if the URL path /WinplusPortal/ws/sWinplus.svc/json/uploadfile is accessible on the web server by reviewing web server configuration files (IIS, Apache, Nginx) or attempting a benign HTTP request to the endpoint.Affected if The endpoint /WinplusPortal/ws/sWinplus.svc/json/uploadfile exists and responds to requests.
-
Confirm file upload functionality is enabledReview application configuration or logs to determine if the uploadfile service endpoint is actively enabled and not disabled through configuration.Affected if The uploadfile service endpoint is enabled and operational in the application.
-
Inspect file upload validation controlsExamine the application's source code, configuration, or web.config/IIS settings for any file type validation logic on the upload endpoint. Look for allowlist or blocklist configurations controlling allowed file extensions.Affected if No file type validation or allowlist controls are implemented for the upload endpoint.
You are affected if the installed WinPlus version is exactly 24.11.27 AND the /WinplusPortal/ws/sWinplus.svc/json/uploadfile endpoint is accessible and lacks file type 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 allowlist-based file validation including magic byte inspection, reject executable file types (.php, .asp, .jsp, .exe, etc.), store uploads outside webroot, and disable script execution in upload directories.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41347 — 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-41347 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