Is this vulnerability remotely exploitable?

Yes. Any party capable of acting as an OIDC client and communicating with the token endpoint over the network can potentially exploit the issue, provided they can obtain or observe relevant authorization codes.

What level of access does an attacker need?

The attacker must control or impersonate an OIDC client that is allowed to call the token endpoint, and must be able to reuse or intercept an authorization code that belongs to another client or should have expired. They do not need direct access to the Pocket ID server itself.

What is the safest general fix pattern?

Enforce strict, independent checks at the token endpoint: bind each authorization code to a single client, validate that the presenting `client_id` matches that binding, verify that the code is not expired and not already used, and reject the request if any of these validations fail.

Severity:

HIGH RISK

(8.5)

Improper Authorization Checks (CWE-863) in Pocket ID OIDC Token Endpoint

CVE-2026-28513

Published:

Mar 10, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Improper Authorization

CWE:

CWE-863

Impact:

Token Theft and Cross-Client Authorization Code Misuse

Severity:

HIGH RISK

(8.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Authorization

CWE:

CWE-863

Impact:

Token Theft and Cross-Client Authorization Code Misuse

Severity:

HIGH RISK

(8.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Improper Authorization Checks (CWE-863) in Pocket ID OIDC Token Endpoint

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal