365-Stealer

365-Stealer Table of Contents About 365-Stealer About Illicit Consent Grant Attack Key Features of 365-Stealer Setup Attacking Environment Automated Azure App Registration Manual Azure App Registration Configuring the Application Creating Client Secrets Adding API Permissions Setting Up 365-Steal...

TokenTacticsV2

root@kitploit: / / / / / / / / | \ / / / / /// / \ / / / / / / / / | | / / / / / / / // / , / / / / / / // // / // // / / | |/ / / / // //||// // /,////// |/ TokenTactics v2 This is an updated version of TokenTactics originally written by Stephan Borosh @rvrsh3ll & Bobby Cooke @0xBoku...

CVE-2026-81921

Concrete CMS 8.5.3 through 9.5.2 enabled the OAuth 2.0 refresh-token grant using the unmodified upstream League grant, which issued new access tokens from a valid refresh token without re-checking the associated account's active status. A user who obtained a refresh token while active could...

EUVD-2026-79287

Concrete CMS 8.5.3 through 9.5.2 enabled the OAuth 2.0 refresh-token grant using the unmodified upstream League grant, which issued new access tokens from a valid refresh token without re-checking the associated account's active status. A user who obtained a refresh token while active could...

CVE-2026-81921

Concrete CMS versions 8.5.3 through 9.5.2 were affected by a flaw in the OAuth 2.0 refresh-token grant . The CMS used the unmodified upstream League grant, which issued new access tokens from a valid refresh token without re-checking the associated account's active status . As a result, a user wh...

CVE-2026-81921 In Concrete CMS 8.5.3 to 9,5,2, OAuth 2.0 Refresh-Token Grant Bypasses Account Status

Concrete CMS 8.5.3 through 9.5.2 enabled the OAuth 2.0 refresh-token grant using the unmodified upstream League grant, which issued new access tokens from a valid refresh token without re-checking the associated account's active status. A user who obtained a refresh token while active could...

CVE-2026-73312

CVE-2026-73312 XenForo before 2.3.13 can leave an OAuth2 refresh token reusable when its parent access token has expired. What happens XenForo intentionally lets a refresh token outlive its short-lived access token. During rotation it creates the replacement token family, then asks the parent...

CVE-2026-88819

In Siglet current and past versions the refresh token handler do not enforce proof of possession of the issuer DID...

EUVD-2026-77577

In Siglet current and past versions the refresh token handler do not enforce proof of possession of the issuer DID...

CVE-2026-88819

In Siglet current and past versions the refresh token handler do not enforce proof of possession of the issuer DID...

CVE-2026-88819

Siglet (current and all past versions) contains a vulnerability in its refresh token handler , which does not enforce proof of possession of the issuer DID. This lack of enforcement means an attacker could potentially use a refresh token without demonstrating control over the associated decentral...

TokenMan

Access and Refresh Token Suite. Token Man is a tool for supporting post-exploitation activities using AAD access and/or refresh tokens. Table of Contents Usage Commands Fetch Search Swap FOCI Application Client ID Map AZ OAuth Usage root@kitploit: usage: tokenman.py -h fetch,search,swap,az,oauth...

langflow-cors-scanner

CVE-2025-34291 — Langflow Origin Validation / CORS Overview Overly permissive CORS config combined with refresh token cookie config allows credential theft...

NPM: n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

NPM: n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution vulnerability discovered by ? in WordPress Npm n8n versions 2.37.7...

n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

Impact The OAuth token endpoint bound an authorization code's first access token to the consented resource, but not its refresh token. Refreshing only checked that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could refres...

EUVD-2026-73162

n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution...

CVE-2026-86073

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.1, the OAuth token endpoint bound an authorization code's first access token to the consented resource but did not bind its refresh token. Refreshing checked only that the requested resource was registered, not that it...

CVE-2026-86073 n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.1, the OAuth token endpoint bound an authorization code's first access token to the consented resource but did not bind its refresh token. Refreshing checked only that the requested resource was registered, not that it...

CVE-2026-86073 n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.1, the OAuth token endpoint bound an authorization code's first access token to the consented resource but did not bind its refresh token. Refreshing checked only that the requested resource was registered, not that it...

CVE-2026-86073

n8n , an open source workflow automation platform, is affected by a per-resource OAuth consent bypass prior to versions 2.37.7 and 2.38.1 . The OAuth token endpoint bound the initial access token to the consented resource but did not bind the refresh token ; upon refreshing, it only verified the ...