dbcve.org
Single Sign On Portal SystemApplication · Wellchoose

CVE-2026-1429

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-26
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
Single Sign-On Portal System developed by WellChoose has a Reflected Cross-site Scripting vulnerability, allowing authenticated remote attackers to execute arbitrary JavaScript codes in user's browser through phishing attacks.

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 confidence

Reflected Cross-site Scripting (XSS) vulnerability in WellChoose's Single Sign-On Portal System allows authenticated attackers to inject arbitrary JavaScript into victim's browsers via crafted URLs, typically delivered through phishing attacks. The vulnerability stems from improper input validation or output encoding of user-supplied parameters in the SSO authentication flow.

MitigationImplement context-aware output encoding for all user inputs and validate/sanitize input parameters before reflecting them in HTTP responses. Deploy Content Security Policy (CSP) headers as defense-in-depth. Since this affects an SSO system, ensure the fix maintains secure session handling.

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
Single Sign On Portal SystemApplication
Affected:< iftop_p4_181

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 if Wellchoose SSO Portal is installed
    Check your web server or application inventory for instances of Wellchoose Single Sign On Portal System. Search for processes or services named 'wellchoose' or 'sso' and review web server logs for requests to SSO-related paths.
    Affected if The system runs Wellchoose SSO Portal and it is network-accessible.
  2. Determine installed version
    Locate the Wellchoose SSO Portal installation directory and check version files, About pages, or administrative interfaces for the version number. Compare the installed version against 'iftop_p4_181'.
    Affected if The installed version is lower than iftop_p4_181.
  3. Verify SSO authentication endpoints are accessible
    Identify the SSO login/portal URL endpoints (typically /login, /sso, /auth, or similar paths). Confirm these endpoints accept user-supplied parameters via URL query strings or form inputs.
    Affected if SSO authentication endpoints accept URL parameters without apparent validation.
  4. Inspect URL parameter handling for reflection
    Submit a test request to the SSO portal with a harmless test string in a URL parameter (e.g., ?test=<script>alert(1)</script> or ?redirect=test). Check if the response reflects the input exactly without encoding.
    Affected if User-supplied parameters are reflected in the HTTP response without HTML encoding.

The environment is affected if Wellchoose SSO Portal System is running a version lower than iftop_p4_181 and the SSO authentication endpoints reflect URL parameters without proper encoding.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement context-aware output encoding for all user inputs and validate/sanitize input parameters before reflecting them in HTTP responses. Deploy Content Security Policy (CSP) headers as defense-in-depth. Since this affects an SSO system, ensure the fix maintains secure session handling.

Recommended fix Moderate confidence

iftop_p4_181

  1. 1. Identify the current version of the Single Sign On Portal System deployed in your environment.
  2. 2. Confirm the current version is below iftop_p4_181.
  3. 3. Obtain the updated version iftop_p4_181 or later from the vendor WellChoose.
  4. 4. Test the upgrade in a non-production environment to verify compatibility.
  5. 5. Schedule a maintenance window and back up the current system configuration.
  6. 6. Apply the upgrade to iftop_p4_181 or latest stable version.
  7. 7. Verify the upgrade was successful and the XSS vulnerability is remediated.
  8. 8. Monitor the system for any issues after the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Single Sign On Portal System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1429 — 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-2026-1429 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