# CVE-2022-31131: Ownership check missing when updating or deleting mail attachments in Nextcloud mail

> Attackers can access or modify other users' mail attachments due to missing ownership checks in the Nextcloud Mail application.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-xhv7-5mhv-299j

## What is CVE-2022-31131?

CVE-2022-31131 is a medium-severity missing authorization vulnerability in nextcloud security-advisories, published on 6 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nextcloud mail is a Mail app for the Nextcloud home server product. Versions of Nextcloud mail prior to 1.12.2 were found to be missing user account ownership checks when performing tasks related to mail attachments. Attachments may have been exposed to incorrect system users. It is recommended that the Nextcloud Mail app is upgraded to 1.12.2. There are no known workarounds for this issue. ### Workarounds No workaround available ### References * [Pull request](https://github.com/nextcloud/mail/pull/6600) * [HackerOne](https://hackerone.com/reports/1579820) ### For more information If you have any questions or comments about this advisory: * Create a post in [nextcloud/security-advisories](https://github.com/nextcloud/security-advisories/discussions) * Customers: Open a support ticket at [support.nextcloud.com](https://support.nextcloud.com)

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-31131?

It affects 1 product.


Products: Nextcloud Nextcloud Mail.

## How do I fix CVE-2022-31131?

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

## Is CVE-2022-31131 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31131 and fix it if it is affected.

What it is: CVE-2022-31131 is a medium-severity missing authorization vulnerability in nextcloud security-advisories, published on 6 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31131 exists.

Affected product: nextcloud security-advisories. 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-2022-31131/ (Markdown: https://insights.sbomify.com/CVE-2022-31131/index.md)
```

## Sources

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

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