# CVE-2025-0885: Incorrect Authorization vulnerability affects OpenText™ GroupWise

> Attackers can bypass access controls to view private calendar items in OpenText GroupWise, compromising user privacy.

- **Severity:** Low 1.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/S:P/AU:Y/R:A/V:D/RE:L/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2025
- **Updated:** 3 Jul 2025
- **Also known as:** GHSA-qv9c-rwmq-rgm5

## What is CVE-2025-0885?

CVE-2025-0885 is a low-severity missing authorization vulnerability in OpenText™ GroupWise, published on 3 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect Authorization vulnerability in OpenText™ GroupWise allows Exploiting Incorrectly Configured Access Control Security Levels.

The vulnerability could allow unauthorized access to calendar items marked private.

This issue affects GroupWise versions 7 through 17.5, 23.4, 24.1, 24.2, 24.3, 24.4.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-0885?


## How do I fix CVE-2025-0885?

No fix has been published for CVE-2025-0885 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0885 being exploited?

There is no known exploitation of CVE-2025-0885 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0885 and fix it if it is affected.

What it is: CVE-2025-0885 is a low-severity missing authorization vulnerability in OpenText™ GroupWise, published on 3 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0885 in the wild and no public exploit code.

Affected product: OpenText™ GroupWise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0885/ (Markdown: https://insights.sbomify.com/CVE-2025-0885/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0885
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0885
- OSV: https://osv.dev/vulnerability/CVE-2025-0885

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0885/
Summaries are generated and may contain mistakes; the official description above is the record.