dbcve.org
TripleplayApplication · Uniguest

CVE-2024-50705

HIGH · 7.1 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 24.1.2 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

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
Unauthenticated reflected cross-site scripting (XSS) vulnerability in Uniguest Tripleplay before 24.2.1 allows remote attackers to execute arbitrary scripts via the page parameter.

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

Unauthenticated reflected cross-site scripting (XSS) vulnerability in Uniguest Tripleplay before version 24.2.1 allows remote attackers to inject malicious JavaScript or HTML via the 'page' parameter. The attack does not require authentication, and the malicious payload is reflected back to the user in the server's response, potentially executing in the victim's browser session.

MitigationUpdate Uniguest Tripleplay to version 24.2.1 or later to patch the vulnerability. As a temporary measure, implement input validation and output encoding on the 'page' parameter, and consider deploying a WAF rule to block XSS attempts.

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
TripleplayApplication
Affected:< 24.1.2= 24.2

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
Adjacent
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:L/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 checks

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

  1. Identify the installed Uniguest Tripleplay version
    Locate the software version information in the application admin interface, system information page, or check the installation files/diagnostics. This is typically found under Help > About, System Settings, or in the installation directory metadata.
    Affected if The installed version is either below 24.1.2 or exactly 24.2 (any build of version 24.2). Versions 24.2.1 and later are not affected.
  2. Confirm the product is Uniguest Tripleplay
    Verify the running application is specifically Uniguest Tripleplay (not another product in the Uniguest portfolio) by checking the product name in the web interface header, login page, or system documentation.
    Affected if The product is confirmed to be Uniguest Tripleplay.
  3. Verify the 'page' parameter is accessible
    Send an HTTP request to the Tripleplay web interface without authentication, including a benign test value in the 'page' parameter (e.g., ?page=test123), and observe if the value is reflected in the response HTML without proper encoding.
    Affected if The 'page' parameter reflects the user-supplied input back into the response without encoding, indicating potential XSS vulnerability.

A user is affected if they are running Uniguest Tripleplay version 24.2 or any version below 24.1.2, and the application reflects the 'page' parameter input directly into HTML responses without sanitization.

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
Upgrade available Upgrade to 24.1.2 or later
Fixed in 24.1.2
Interim mitigation

Update Uniguest Tripleplay to version 24.2.1 or later to patch the vulnerability. As a temporary measure, implement input validation and output encoding on the 'page' parameter, and consider deploying a WAF rule to block XSS attempts.

Recommended fix High confidence

24.2.1

  1. 1. Identify current Tripleplay installation version via admin console or system information
  2. 2. If version is < 24.1.2 or = 24.2, plan upgrade to version 24.2.1
  3. 3. Review Tripleplay 24.2.1 release notes for any prerequisites
  4. 4. Perform full backup of current configuration and database
  5. 5. Execute upgrade to version 24.2.1 following vendor documentation
  6. 6. Verify successful installation by checking version number in admin interface
  7. 7. Test the 'page' parameter functionality to confirm fix and normal operation
Caveat Review release notes for 24.2.1 - may include configuration changes or deprecations requiring testing

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

Fix this in Tripleplay Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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