# CVE-2026-3020: Identity based authorization bypass vulnerability (IDOR) in the Wakyma application web

> Attackers can bypass authorization to modify user data and take over accounts in the Wakyma web application.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA: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:** 16 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-832q-9r5f-ppx5

## What is CVE-2026-3020?

CVE-2026-3020 is a high-severity missing authorization vulnerability in Wakyma application web, published on 16 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Identity based authorization bypass vulnerability (IDOR) that allows an attacker to modify the data of a legitimate user account, such as changing the victim's email address, validating the new email address, and requesting a new password. This could allow them to take complete control of other users' legitimate accounts

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-3020 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3020 is a high-severity missing authorization vulnerability in Wakyma application web, published on 16 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3020 in the wild and no public exploit code.

Affected product: Wakyma application web. 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-3020/ (Markdown: https://insights.sbomify.com/CVE-2026-3020/index.md)
```

## Sources

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

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