# CVE-2023-46699: Cross-site request forgery (CSRF) vulnerability exists in the User settings (/me) page of GROWI versions prior to v6.0.0.


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Dec 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-5q4h-2vw3-5vc3

## What is CVE-2023-46699?

CVE-2023-46699 is a medium-severity vulnerability in WESEEK, Inc. GROWI, published on 26 Dec 2023. 

### Official description

Cross-site request forgery (CSRF) vulnerability exists in the User settings (/me) page of GROWI versions prior to v6.0.0. If a user views a malicious page while logging in, settings may be changed without the user's intention.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-46699?

It affects 1 product.


Products: Weseek Growi.

## How do I fix CVE-2023-46699?

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

## Is CVE-2023-46699 being exploited?

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

## Other vulnerabilities in WESEEK, Inc. GROWI

- [CVE-2021-20736](https://insights.sbomify.com/CVE-2021-20736/): SQL injection in GROWI (critical 9.1)
- [CVE-2019-5968](https://insights.sbomify.com/CVE-2019-5968/): Cross-site request forgery in GROWI (high 8.8)
- [CVE-2021-20670](https://insights.sbomify.com/CVE-2021-20670/): Information disclosure in GROWI (high 7.5)
- [CVE-2020-5682](https://insights.sbomify.com/CVE-2020-5682/): Denial of service in GROWI (high 7.5)
- [CVE-2020-5683](https://insights.sbomify.com/CVE-2020-5683/): Path traversal in GROWI (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46699 and fix it if it is affected.

What it is: CVE-2023-46699 is a medium-severity vulnerability in WESEEK, Inc. GROWI, published on 26 Dec 2023. 
Exploitation: There is no known exploitation of CVE-2023-46699 in the wild and no public exploit code.

Affected product: WESEEK, Inc. GROWI. 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-2023-46699/ (Markdown: https://insights.sbomify.com/CVE-2023-46699/index.md)
```

## Sources

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

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