Security readout for executives and security teams
Plain-English summary
Code by Zapier previously let a lower-privileged user inside the same company account gain broader access through its code-execution environment. The main business risk was internal overreach: employees with limited roles could potentially reach credentials, secrets, or automations meant for other users.
Executive priority
Treat this as a high-priority historical exposure review if your organization used Code by Zapier before 2022-08-17 with shared accounts or embedded secrets. Current urgency depends on whether sensitive credentials remain unchanged since that period.
Technical view
CVE-2022-28802 is a CWE-732 permission issue in Code by Zapier before 2022-08-17. The service exposed a customer-controlled general-purpose VM that did not properly enforce intra-account role-based access control, allowing privilege escalation including Python or JavaScript execution.
Likely exposure
Exposure is most relevant to organizations that used Code by Zapier before 2022-08-17 in shared company accounts, especially where automations stored credentials or secrets that were not intended for all account users.
Exploitation context
The CVSS vector shows network access, low privileges, no user interaction, and high confidentiality, integrity, and availability impact. The source bundle does not indicate CISA KEV listing or confirmed active exploitation.
Researcher notes
The record names no CPEs and lists affected vendor/product as n/a, so product scoping depends on the CVE description and Zenity disclosures. Evidence supports intra-account privilege escalation, not cross-tenant compromise. No source in the bundle confirms active exploitation.
Mitigation direction
- Confirm current Zapier guidance for CVE-2022-28802 and related disclosures.
- Identify Code by Zapier use before 2022-08-17.
- Separate automations containing sensitive credentials into appropriately isolated accounts or environments.
- Review and rotate secrets that may have been exposed to unintended account users.
- Limit Code by Zapier access to users with a clear business need.
Validation and detection
- Inventory Zaps using Python or JavaScript code steps before 2022-08-17.
- Identify company account users with access during the affected period.
- Map which automations contained credentials, tokens, or other sensitive secrets.
- Review available Zapier activity records for unexpected edits or executions.
- Confirm role-based access expectations against current Zapier behavior and vendor documentation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-28802 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.zenity.io/blog/zapescape-organization-wide-control-over-code-by-zapier/CVE reference · x_refsource_MISC
- https://www.zenity.io/blog/zapescape-vulnerability-disclosure/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.