dbcve.org
WinplusApplication · Iest

CVE-2025-41349

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Stored 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/savesolpla_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 · high confidence

A stored Cross-site Scripting (XSS) vulnerability exists in WinPlus v24.11.27 where the 'descripcion' parameter in the '/WinplusPortal/ws/sWinplus.svc/json/savesolpla_post' endpoint does not properly validate user input. An attacker can inject malicious JavaScript through a crafted POST request that persists on the server and executes when other authenticated users view the content, allowing session cookie theft.

MitigationImplement proper input validation and output encoding on the 'descripcion' parameter server-side, including contextual encoding for web outputs andContent Security Policy headers to mitigate XSS exploitation.

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
WinplusApplication
Affected:= 24.11.27

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify WinPlus version
    Check the application version displayed in the WinPlus portal interface, typically found in the Help > About section, or check version information in the application metadata/configuration files.
    Affected if The installed version is exactly 24.11.27 (Iest Winplus)
  2. Verify the affected endpoint exists
    Inspect the web application's URL structure and confirm the path '/WinplusPortal/ws/sWinplus.svc/json/savesolpla_post' is accessible or present in the deployed web root.
    Affected if The endpoint /WinplusPortal/ws/sWinplus.svc/json/savesolpla_post exists and is routable within the application
  3. Confirm 'descripcion' parameter is processed
    Check if the 'savesolpla_post' functionality is enabled in the WinPlus portal, typically related to solution/plan submission features where a description field would be used.
    Affected if The savesolpla_post functionality is available and accepts user input in the 'descripcion' parameter
  4. Check authentication requirements on the endpoint
    Review the web application configuration (web.config or equivalent) to determine if the endpoint requires authentication, and test whether authenticated users can submit data through this endpoint.
    Affected if The endpoint accepts requests from authenticated users without proper input validation on the 'descripcion' parameter

You are affected if you are running Iest Winplus version 24.11.27 and the savesolpla_post endpoint that accepts the 'descripcion' parameter is accessible within your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on the 'descripcion' parameter server-side, including contextual encoding for web outputs andContent Security Policy headers to mitigate XSS exploitation.

Fix this in Winplus Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41349 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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