CVE-2025-50708
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 · uneditedAn issue in Perplexity AI GPT-4 v.2.51.0 allows a remote attacker to obtain sensitive information via the token component in the shared chat URL
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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in Perplexity AI's shared chat functionality. The application exposes a token in the shared chat URL that can be manipulated by a remote attacker to access sensitive information from other users' chat sessions without proper authorization. The token component lacks sufficient access control validation, allowing unauthorized access to chat data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify shared chat feature usageLocate any shared chat URLs or endpoints in your Perplexity AI environment. Check browser history, saved links, or shared conversation records for URLs containing a token or identifier parameter.Affected if Shared chat URLs exist that include a token or unique identifier in the URL path or query string.
-
Examine token exposure in shared URLsReview the structure of shared chat URLs. Identify whether the URL contains a predictable token value (such as a UUID, base64 string, or sequential identifier) that could be extracted and manipulated.Affected if Shared chat URLs expose a token value that is visible in the URL without additional authentication layers.
-
Test unauthorized token accessCopy a token from an existing shared chat URL and attempt to access it from an authenticated session under a different user account, or from an incognito/private browser window without being logged in.Affected if The shared chat content loads successfully without verifying that the requesting user owns or has permission to access that specific token.
-
Verify access control on shared chat endpointsIntercept shared chat HTTP requests and examine whether the server performs authorization checks validating token ownership before returning chat data. Check for HTTP response codes and data returned.Affected if The server returns chat data for a shared token without rejecting the request based on user identity or permissions.
Your environment is affected if shared chat URLs expose tokens that can be accessed by unauthorized users without proper ownership or permission validation.
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 authorization checks to validate that the requesting user owns or has permission to access the shared chat token. Additionally, consider rotating exposed tokens, implementing token expiration, and adding referrer/origin validation for shared chat endpoints.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50708 — 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-50708 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