# CVE-2022-27978: Business logic in n/a

> Attackers can arbitrarily reset user passwords in Tooljet by exploiting improper handling of missing API values, leading to account takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-wxm6-gcq6-r4p5

## What is CVE-2022-27978?

CVE-2022-27978 is a high-severity vulnerability in n/a, published on 26 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tooljet v1.6 does not properly handle missing values in the API, allowing attackers to arbitrarily reset passwords via a crafted HTTP request.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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

It affects 1 product.


Products: Tooljet Tooljet.

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

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

## Is CVE-2022-27978 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-3422](https://insights.sbomify.com/CVE-2022-3422/): Improper Privilege Management in tooljet/tooljet (critical 9.8)
- [CVE-2022-2631](https://insights.sbomify.com/CVE-2022-2631/): Improper Access Control in tooljet/tooljet (critical 9.8)
- [CVE-2022-2037](https://insights.sbomify.com/CVE-2022-2037/): Excessive Attack Surface in tooljet/tooljet (critical 9.8)
- [CVE-2022-23067](https://insights.sbomify.com/CVE-2022-23067/): ToolJet - Token Leakage via Referer Header (high 8.8)
- [CVE-2022-3019](https://insights.sbomify.com/CVE-2022-3019/): Improper Access Control in tooljet/tooljet (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27978 is a high-severity vulnerability in n/a, published on 26 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-27978 exists.

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

## Sources

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

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