dbcve.org
TripleplayApplication · Uniguest

CVE-2023-25760

HIGH · 8.8 CVSS v3.1 Published 2023-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Incorrect Access Control in Tripleplay Platform releases prior to Caveman 3.4.0 allows authenticated user to modify other users passwords via a crafted request payload

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

The Tripleplay Platform prior to version Caveman 3.4.0 contains an Incorrect Access Control vulnerability where an authenticated user can modify other users' passwords by sending a crafted request payload. This indicates a broken authorization check (likely an Insecure Direct Object Reference or IDOR) where the application fails to verify that the requesting user has permission to modify the target user's credentials.

MitigationUpgrade to Tripleplay Platform Caveman 3.4.0 or later which contains the access control fix. Until patched, monitor authentication logs for unauthorized password modification attempts and consider implementing additional authorization middleware on password change endpoints.

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:= 3.4.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 installed Tripleplay Platform version
    Locate the version information for the Tripleplay Platform installation, typically found in the platform's About section, system information page, or configuration files. Check release notes or the software inventory if available.
    Affected if The installed version is exactly 3.4.0 (the only version explicitly listed as affected).
  2. Verify password modification endpoint accessibility
    Confirm whether the password change or user credential modification endpoint is exposed and enabled in the platform. This may be accessible via the web interface API or administrative console.
    Affected if The password modification endpoint is accessible and functional in the deployed version.
  3. Review authorization controls on password change functionality
    Inspect the application's access control configuration or code related to password modification endpoints. Determine if the system validates that the requesting user owns the target account or has administrative privileges before allowing password changes.
    Affected if The system does not validate ownership or permissions before allowing password modifications (no proper authorization check exists).
  4. Examine authentication logs for password modification anomalies
    Review authentication and audit logs for password change events, particularly those where the modifying user differs from the target user account.
    Affected if Logs show password modifications performed on accounts by users other than the account owner or administrators.

A user is affected if they are running Tripleplay Platform version 3.4.0 and the password modification endpoint lacks proper authorization checks to verify the requesting user has permission to modify the target user's credentials.

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

Upgrade to Tripleplay Platform Caveman 3.4.0 or later which contains the access control fix. Until patched, monitor authentication logs for unauthorized password modification attempts and consider implementing additional authorization middleware on password change endpoints.

Recommended fix Moderate confidence

Caveman 3.4.0 or later

  1. Obtain the Tripleplay Caveman 3.4.0 release or later from official Tripleplay distribution channels
  2. Review Tripleplay upgrade documentation for your deployment type
  3. Plan maintenance window as upgrades may require service interruption
  4. Execute upgrade following vendor-provided procedures
  5. Verify the upgrade was successful by confirming version number
  6. Test that the access control fix prevents authenticated users from modifying other users passwords

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

Fix this in Tripleplay Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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