Twenty
Twenty: Field-level read bypass
Twenty is an open-source CRM (customer relationship management) platform. Prior to 2.22.0, field-level read permission is enforced on selected output fields but not on GraphQL or REST filter predicates. A workspace member or API key with permission to read an object but not a particular field can reference that denied field in direct filters, relation filters, or persisted view filters. The resulting totalCount and row presence reveal whether guesses match the real column, forming a boolean/count oracle that can reconstruct denied field values for records exposed by the principal's row-level policy. This issue is fixed in version 2.22.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.22.0
Fixed in 2.22.0
Mitigation
Upgrade twenty to 2.22.0 or later.
References
- Vendor advisory github.com/twentyhq/twenty/security/advisories…
- Patch github.com/twentyhq/twenty/pull/22873
- Patch github.com/twentyhq/twenty/commit/a5108d512f75…
1 more
- Release notes github.com/twentyhq/twenty/releases/tag/twenty…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.