CVE-2025-51867
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 · uneditedInsecure Direct Object Reference (IDOR) vulnerability in Deepfiction AI (deepfiction.ai) thru June 3, 2025, allowing attackers to chat with the LLM using other users' credits via sensitive information gained by the /browse/stories endpoint.
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 confidenceIDOR vulnerability in Deepfiction AI allows attackers to access other users' credits by manipulating object references obtained from the /browse/stories endpoint, enabling unauthorized LLM chat interactions using compromised user accounts.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Deepfiction AI installation and versionLocate the Deepfiction AI application installation directory or check the application's version information (often in package.json, setup files, or the application's About page)Affected if The installed version cannot be confirmed as patched because no fixed version is specified in the advisory
-
Verify the /browse/stories endpoint existsAccess the /browse/stories endpoint in the application (e.g., curl or browse to https://[host]/browse/stories)Affected if The endpoint returns HTTP 200 and displays story listings with object references such as story IDs or credit identifiers
-
Check if endpoint exposes object referencesInspect the response from /browse/stories for direct object references (story IDs, credit references, user identifiers) that could be manipulatedAffected if The endpoint returns predictable or sequential object identifiers that could be modified to access other users' resources
-
Test authorization on credit-related actionsAttempt to access or modify credit information using object references from another user account, or intercept requests to /chat/llm endpoints and modify user/credit parametersAffected if The application allows access to credit data or LLM chat interactions without proper ownership verification (returns success instead of 403 Forbidden)
-
Review API responses for sensitive information exposureCompare responses from /browse/stories when accessed by different user accounts - check if credit balances or user-specific data is exposed in the story listingsAffected if Story browsing responses contain other users' credit information or sensitive account data that should not be visible to the requesting user
If the /browse/stories endpoint is accessible and returns object references that can be manipulated to access other users' credits without authorization checks, the environment is affected by this IDOR vulnerability.
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 verify user ownership of credits before allowing LLM chat interactions, and restrict sensitive information exposure in the /browse/stories endpoint.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-51867 — 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-51867 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