CVE-2025-41350
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 · uneditedStored Cross-site Scripting (XSS)vylnerability type in WinPlus v24.11.27 byInformática del Este that consist of an stored XSS of a stored XSS due to a lack of proper validation of user input by sending a POST request using the 'descripcion' parameter in '/WinplusPortal/ws/sWinplus.svc/json/savesoldoc_post'. This vulnerability could allow a remote user to send a specially crafted query to an authenticated user and steal their cookie session details.
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 confidenceStored XSS vulnerability in WinPlus v24.11.27 where the 'descripcion' parameter in the /WinplusPortal/ws/sWinplus.svc/json/savesoldoc_post endpoint does not properly validate user input, allowing malicious scripts to be stored and executed in authenticated users' browsers to steal session cookies.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 installed Winplus versionLocate the Winplus installation directory and check the version file, or query the application's about/version information. Common paths may include C:\Program Files\Iest\Winplus or the application's main executable properties.Affected if The installed version is exactly 24.11.27 (Iest Winplus)
-
Verify WinplusPortal web service is accessibleConfirm the WinplusPortal web application is running and the endpoint /WinplusPortal/ws/sWinplus.svc/json/savesoldoc_post is accessible via HTTP/HTTPS from the application server.Affected if The WinplusPortal endpoint is reachable and responds to requests
-
Check savesoldoc_post endpoint configurationReview the web server configuration (IIS or other) to confirm the savesoldoc_post JSON endpoint is enabled and exposed. Inspect web.config or equivalent for endpoint routing.Affected if The savesoldoc_post endpoint is exposed and accepts the 'descripcion' parameter
-
Review application logs for suspicious descripcion parameter usageExamine application and web server logs for any POST requests to /WinplusPortal/ws/sWinplus.svc/json/savesoldoc_post containing unusual characters or patterns in the 'descripcion' parameter that may indicate exploitation attempts.Affected if Logs show exploitation attempts or stored malicious payloads in the descripcion field
You are affected if the installed Iest Winplus version is exactly 24.11.27 and the WinplusPortal savesoldoc_post endpoint is accessible and processes the descripcion parameter.
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 proper input validation and output encoding for the 'descripcion' parameter, and add context-aware escaping when displaying stored data to prevent XSS execution.
- 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-41350 — 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-41350 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