Is CVE-2026-25083 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-25083 being exploited in the wild.

How severe is CVE-2026-25083?

High severity, with a CVSS score of 8.3, published 16 March 2026.

Which products and versions are affected?

GROWI, Inc. GROWI v7.4.5 and earlier.

Is there a fix for CVE-2026-25083?

A patch was published on 2026-03-16: Fixed in v7.4.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-25083 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-25083?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-25083: GROWI missing authorization in OpenAI thread and message API

CVE-2026-25083 · Severity: high · CVSS 8.3 · Published 2026-03-16

GROWI is an open-source wiki and collaboration platform. A security flaw in its AI assistant integration allows logged-in users to view or modify the private chat threads and messages of other users. This could lead to the exposure of sensitive internal discussions or the unauthorized alteration of shared information if an attacker knows the identifier of a shared AI assistant.

Quick answers

Is CVE-2026-25083 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-25083 being exploited in the wild.
How severe is CVE-2026-25083?: High severity, with a CVSS score of 8.3, published 16 March 2026.
Which products and versions are affected?: GROWI, Inc. GROWI v7.4.5 and earlier.
Is there a fix for CVE-2026-25083?: A patch was published on 2026-03-16: Fixed in v7.4.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-25083 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-25083?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A missing authorization vulnerability (CWE-862) exists in the OpenAI thread and message API endpoints of GROWI. The root cause is a failure to verify if the requesting user has permission to access or modify a specific thread or message. An authenticated attacker with network access can exploit this by supplying the identifier of a shared AI assistant to interact with data belonging to other users. This allows for unauthorized viewing (Confidentiality) and tampering (Integrity) of AI-related communications. The issue is resolved in GROWI v7.4.6.

Affected products

GROWI, Inc. GROWI v7.4.5 and earlier

Timeline

2026-03-16: disclosed
2026-03-16: advisory
2026-03-16: patched: Fixed in v7.4.6

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.