dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-51865

HIGH · 8.8 CVSS v3.1 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Ai2 playground web service (playground.allenai.org) LLM chat through 2025-06-03 is vulnerable to Insecure Direct Object Reference (IDOR), allowing attackers to gain sensitvie information via enumerating thread keys in the 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 · high confidence

The Ai2 playground web service (playground.allenai.org) contains an Insecure Direct Object Reference (IDOR) vulnerability in its LLM chat functionality through June 3, 2025. The vulnerability allows attackers to access sensitive information from other users' chat threads by enumerating predictable thread keys in the URL, without proper authorization validation.

MitigationImplement proper authorization checks to verify that the requesting user owns or has permission to access the specific thread before returning any data, and add rate limiting to prevent enumeration attacks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if you run the Ai2 playground service
    Search your infrastructure for instances of the Ai2 playground web application (playground.allenai.org or self-hosted variants). Check running services, container images, or deployed applications for 'ai2-playground' or related package names.
    Affected if You operate a deployment of the Ai2 playground service accessible over the network.
  2. Determine the deployment date or version
    Review your deployment records, git tags, or container image timestamps. Compare the deployment date against June 3, 2025, or check if your version predates the patched release.
    Affected if Your Ai2 playground instance was deployed or last updated before the June 3, 2025 security patch date.
  3. Inspect thread access endpoint behavior
    Access your playground instance, create multiple chat threads, and observe the URL structure for thread identifiers. Attempt to access a thread ID that does not belong to your account by modifying the thread key in the URL (e.g., /chat/thread/12345 to /chat/thread/12346).
    Affected if The service returns data from a thread belonging to another user without returning a 403 Unauthorized or 404 Not Found error.
  4. Check for authorization validation in thread endpoints
    Review the source code or API configuration for chat thread endpoints (typically /api/thread/{id} or similar). Verify that every thread access request includes a check confirming the authenticated user owns the requested thread before returning any data.
    Affected if Thread endpoints lack ownership verification logic, or the authorization check occurs after data retrieval rather than before.
  5. Audit logs for thread enumeration patterns
    Review access logs for repeated requests to sequential or nearby thread IDs from the same IP address or session, which would indicate enumeration attempts.
    Affected if Logs show requests cycling through sequential thread IDs without corresponding authentication changes, suggesting the thread parameter is predictable and unprotected.

You are affected if you operate an Ai2 playground instance deployed before June 3, 2025 where thread access lacks proper ownership validation, allowing unauthorized users to view other users' chat threads by modifying thread identifiers in the URL.

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 authorization checks to verify that the requesting user owns or has permission to access the specific thread before returning any data, and add rate limiting to prevent enumeration attacks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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