CVE-2022-28802
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCode 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.)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCode by Zapier provided a customer-controlled virtual machine for Python/JavaScript execution that inadvertently granted all users within a company account full access to all account resources, bypassing role-based access controls. This allowed intra-account privilege escalation where any user could access secrets, credentials, and execute code with permissions beyond their intended role.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2022-08-17CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Code by Zapier feature usageReview your Zapier account audit logs or workflow editor to determine if any Zaps utilize the Code by Zapier action (Python or JavaScript) for executing custom scripts.Affected if Code by Zapier is actively used in workflows and the account was created or last updated before 2022-08-17.
-
Confirm account type is multi-user company accountCheck the Zapier account settings under Team or Users section to verify if this is a company account with multiple team members who have different role assignments.Affected if A company account with multiple users and the Code feature is in use.
-
Review account creation or last security review dateLocate the account creation timestamp or the date of the last security/permission review in the account settings or admin dashboard.Affected if The account was established or has not been reviewed since before August 17, 2022.
-
Inspect audit logs for cross-user resource accessExamine Zapier audit logs or execution history for instances where a user executed Code actions that accessed secrets, credentials, or data belonging to other users or roles within the same account.Affected if Audit logs show code executions accessing resources outside the executing user's assigned role scope.
-
Check for unauthorized secret or credential retrievalSearch audit or history logs for Code by Zapier actions that retrieved stored credentials, API keys, or secrets from the account's credential store.Affected if Code actions retrieved credentials without corresponding workflow ownership or role justification.
You are affected if Code by Zapier is enabled in a multi-user company account that existed before the 2022-08-17 patch date and audit logs show users accessing resources outside their assigned roles.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2022-08-17
Migrate sensitive workflows requiring credential isolation to separate Zapier accounts until the vendor's patch (post-2022-08-17) is verified, and confirm proper account-level isolation is enforced in the Code feature.
Code by Zapier version 2022-08-17 or later (vendor-managed SaaS - no customer action required for patch deployment)
- Verify that your Code by Zapier account is running a version dated 2022-08-17 or later by checking Zapier's platform or contacting Zapier support
- Review all Code by Zapier applications that were created or modified before August 2022 for any unintended access to secrets or credentials
- Audit user permissions within your Zapier account to ensure role-based access controls are properly configured
- If you previously worked around this issue by using separate Zapier accounts for isolation, you can now consolidate if desired after confirming the fix is applied
- Contact Zapier support to confirm your account received the security update if uncertainty exists
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28802 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data