tinacms auth/next-tinacms-azure Authentication Provider index.ts isAuthorized clientID improper authorization

Summaryinfo

A vulnerability, which was classified as critical, has been found in tinacms auth and next-tinacms-azure. Affected is the function isAuthorized of the file packages/@tinacms/auth/src/index.ts of the component Authentication Provider. This manipulation of the argument clientID causes improper authorization. This vulnerability is handled as CVE-2026-63506. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in tinacms auth and next-tinacms-azure (affected version unknown). It has been declared as critical. Affected by this vulnerability is the function isAuthorized of the file packages/@tinacms/auth/src/index.ts of the component Authentication Provider. The manipulation of the argument clientID with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Tina is a headless content management system. Prior to @tinacms/auth 1.1.4 and next-tinacms-azure 15.0.1, isAuthorized accepts a request-controlled clientID and asks isUserAuthorized to validate the bearer token against that selected TinaCloud app instead of the self-hosted site's configured app. An attacker with any TinaCloud account can submit the attacker's own app ID and valid token to a victim endpoint, causing TinaCloudBackendAuthProvider or an affected media authorized callback to accept the attacker's verified status across the tenant boundary. The vulnerable logic is present in packages/@tinacms/auth/src/index.ts and packages/next-tinacms-azure/src/auth.ts. Successful exploitation permits media listing, reading, upload, or deletion and, when TinaCloudBackendAuthProvider is used, GraphQL read, create, update, and delete operations on the victim's content without a victim account or victim interaction. This vulnerability is fixed in @tinacms/auth 1.1.4 and next-tinacms-azure 15.0.1.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-63506 since 07/16/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/16/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• tinacms

Name

• auth
• next-tinacms-azure

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion