# CVE-2022-1236: Weak Password Requirements in weseek/growi

> Weak password requirements in GROWI allow attackers to guess credentials and take over user accounts.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 5 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-qxh2-x3x4-mxxw

## What is CVE-2022-1236?

CVE-2022-1236 is a medium-severity vulnerability in weseek/growi, published on 5 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Weak Password Requirements in GitHub repository weseek/growi prior to v5.0.0.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Weseek Growi.

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

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

## Is CVE-2022-1236 being exploited?

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

## Other vulnerabilities in weseek/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-2022-1236 and fix it if it is affected.

What it is: CVE-2022-1236 is a medium-severity vulnerability in weseek/growi, published on 5 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1236 in the wild and no public exploit code.

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

## Sources

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

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