How widely exploitable is this vulnerability?

The flaw is remotely exploitable wherever the affected JwtAuthenticationTokenFilter is exposed over HTTP. Any client capable of reaching the application and manipulating the `mock-token` argument may attempt to bypass authentication.

Does an attacker need valid credentials to exploit this issue?

In typical scenarios, no prior credentials are required. The vulnerability arises because the filter incorrectly trusts or mishandles the `mock-token` input, allowing unauthenticated users to appear authenticated.

What is the safest general fix pattern?

The safest approach is to remove or strictly isolate any mock or non-standard authentication paths from production code. Authentication decisions should always be based on fully validated tokens or credentials, with explicit checks ensuring that test-only mechanisms cannot be triggered by arbitrary clients.

Severity:

HIGH RISK

(7.3)

Improper Authentication (CWE-287) in JwtAuthenticationTokenFilter of yudao-cloud Ruoyi-Vue-Pro

CVE-2026-7710

Published:

May 3, 2026

Status:

Deferred

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-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Authentication Bypass / Unauthorized Access

Severity:

HIGH RISK

(7.3)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Authentication Bypass / Unauthorized Access

Severity:

HIGH RISK

(7.3)

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 Authentication (CWE-287) in JwtAuthenticationTokenFilter of yudao-cloud Ruoyi-Vue-Pro

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.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

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