fuyang_lipengjun platform 1.0 /brand/queryAll BrandController improper authorization

Summaryinfo

A vulnerability marked as problematic has been reported in fuyang_lipengjun platform 1.0. Affected by this vulnerability is the function BrandController of the file /brand/queryAll. The manipulation leads to improper authorization. This vulnerability is uniquely identified as CVE-2025-10676. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in fuyang_lipengjun platform 1.0 and classified as problematic. This issue affects the function BrandController of the file /brand/queryAll. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality.

The advisory is shared at cnblogs.com. The identification of this vulnerability is CVE-2025-10676. The exploitation is known to be easy. The attack may be initiated remotely. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

The exploit is available at cnblogs.com. It is declared as proof-of-concept.

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

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 4.3
CNA Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper authorization
CWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

09/18/2025 Advisory disclosed
09/18/2025 +0 days VulDB entry created
09/19/2025 +1 days VulDB entry last update

Sourcesinfo

Advisory: cnblogs.com
Status: Not defined

CVE: CVE-2025-10676 (🔒)
GCVE (CVE): GCVE-0-2025-10676
GCVE (VulDB): GCVE-100-324797
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 09/18/2025 07:57
Updated: 09/19/2025 16:57
Changes: 09/18/2025 07:57 (55), 09/19/2025 16:57 (30)
Complete: 🔍
Submitter: lucasg2g
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #653344: fuyang_lipengjun platform v1.0 broken function level authorization (by lucasg2g)

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!