# CVE-2026-125388: Group-Office before 6.8.181, 25.0.116, and 26.0.58 Missing Authorization in Forms Report Download


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-42qf-m3j9-837r, GHSA-mp2v-gg3m-qvpx

## What is CVE-2026-125388?

CVE-2026-125388 is a high-severity vulnerability in Intermesh Group-Office, published on 9 Nov 2026. 

### Official description

Intermesh Group-Office before 6.8.181, 25.0.116, and 26.0.58 contains a missing authorization vulnerability that allows authenticated users to download form reports via api/download.php without permission checks. Attackers can request the business/forms/report blob with a form ID to export every submission as an XLSX file, disclosing submissions they are not permitted to see.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-125388?


## How do I fix CVE-2026-125388?

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

## Is CVE-2026-125388 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125388 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125388 and fix it if it is affected.

What it is: CVE-2026-125388 is a high-severity vulnerability in Intermesh Group-Office, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125388 exists.

Affected product: Intermesh Group-Office. 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-2026-125388/ (Markdown: https://insights.sbomify.com/CVE-2026-125388/index.md)
```

## Sources

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

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