How exploitable is this vulnerability in practice?

Exploitability depends on how easily an attacker can obtain or reuse a token accepted by the getinfobytoken API. If tokens are exposed through logs, URLs, weak client storage, or predictable generation, exploitation can be straightforward because the endpoint trusts any valid token.

Does an attacker need administrator access to exploit this?

Not necessarily. The core problem is that the endpoint does not properly distinguish between token holders; a non-admin token or even a generic token may be sufficient if authorization is not enforced beyond basic validity checks.

What is the safest general fix pattern?

Introduce robust authorization controls around the getinfobytoken API so that it verifies both *who* is making the request and *what* they are allowed to access, and limit the returned fields to the minimum required, especially for administrator data.

Severity:

HIGH RISK

(7.5)

Improper Access Control (CWE-284) in blog.admin getinfobytoken API Exposes Admin Data

CVE-2026-30689

Published:

Mar 27, 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-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Sensitive Information Disclosure and Potential Account Compromise

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Sensitive Information Disclosure and Potential Account Compromise

Severity:

HIGH RISK

(7.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 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Improper Access Control (CWE-284) in blog.admin getinfobytoken API Exposes Admin Data

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

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare