CVE-2026-25083
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 · uneditedGROWI OpenAI thread/message API endpoints do not perform authorization. Affected are v7.4.5 and earlier versions. A logged-in user who knows a shared AI assistant's identifier may view and/or tamper the other user's threads/messages.
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 confidenceGROWI versions 7.4.5 and earlier contain an Insecure Direct Object Reference (IDOR) vulnerability in the OpenAI thread/message API endpoints. The affected endpoints lack proper authorization checks, allowing any authenticated user who knows a shared AI assistant's identifier to view or modify threads and messages belonging to other users.
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
- High
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
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 GROWI installation and versionCheck the installed GROWI version by reviewing package.json, docker image tags, or the /_api/v3/version endpoint if available. Compare against affected versions: 7.4.5 and earlier.Affected if The installed version is 7.4.5 or any earlier version of GROWI.
-
Verify OpenAI integration is enabledInspect GROWI configuration settings (environment variables, admin panel, or config file) for any OpenAI-related settings such as OPENAI_API_KEY, GROWI_AI_ENABLED, or AI Assistant configurations.Affected if OpenAI integration or AI Assistant features are enabled in the GROKI instance.
-
Confirm user authentication is activeCheck whether GROWI has user authentication configured and that the system allows user logins, as the IDOR vulnerability requires an authenticated user to exploit.Affected if User authentication is enabled and users can log in to the GROWI instance.
-
Check for shared AI assistant configurationsReview GROWI admin or AI assistant settings to determine if any shared AI assistants with identifiable thread/message access are configured.Affected if Shared AI assistants exist in the environment where one user could potentially know another user's thread identifier.
The environment is affected if running GROWI version 7.4.5 or earlier with OpenAI integration enabled and user authentication active, allowing any logged-in user to potentially access other users' AI assistant threads via the vulnerable endpoints.
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 validation on all OpenAI thread/message API endpoints to verify the requesting user owns or has permission to access the requested resource before returning or modifying any data.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25083 — 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-2026-25083 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