# CVE-2022-28802: Privilege escalation in n/a

> Attackers can escalate privileges to execute arbitrary code within the shared Zapier Code environment, bypassing intended role-based access controls.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 21 Sep 2022
- **Updated:** 27 May 2025
- **Also known as:** GHSA-2g9m-cfmh-9r83

## What is CVE-2022-28802?

CVE-2022-28802 is a high-severity vulnerability in n/a, published on 21 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Code by Zapier before 2022-08-17 allowed intra-account privilege escalation that included execution of Python or JavaScript code. In other words, Code by Zapier was providing a customer-controlled general-purpose virtual machine that unintentionally granted full access to all users of a company's account, but was supposed to enforce role-based access control within that company's account. Before 2022-08-17, a customer could have resolved this by (in effect) using a separate virtual machine for an application that held credentials - or other secrets - that weren't supposed to be shared among all of its employees. (Multiple accounts would have been needed to operate these independent virtual machines.)

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Zapier Code by Zapier.

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

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

## Is CVE-2022-28802 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28802 is a high-severity vulnerability in n/a, published on 21 Sep 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-28802 in the wild and no public exploit code.

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

## Sources

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

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