fuyang_lipengjun platform 1.0 /topic/queryAll TopicController improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in fuyang_lipengjun platform 1.0. The affected element is the function TopicController of the file /topic/queryAll. This manipulation causes improper authorization.
This vulnerability is tracked as CVE-2025-10820. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability was found in fuyang_lipengjun platform 1.0. It has been declared as problematic. Affected by this vulnerability is the function TopicController of the file /topic/queryAll. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality.
The advisory is shared at cnblogs.com. This vulnerability is known as CVE-2025-10820. The exploitation appears to be easy. The attack can be launched remotely. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
It is possible to download the exploit 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB 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: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/21/2025 Advisory disclosed09/21/2025 VulDB entry created
09/23/2025 VulDB entry last update
Sources
Advisory: cnblogs.comStatus: Not defined
CVE: CVE-2025-10820 (🔒)
GCVE (CVE): GCVE-0-2025-10820
GCVE (VulDB): GCVE-100-325177
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/21/2025 18:04Updated: 09/23/2025 12:35
Changes: 09/21/2025 18:04 (55), 09/23/2025 12:35 (30)
Complete: 🔍
Submitter: aibot88
Cache ID: 216::103
Submit
Accepted
- Submit #653741: fuyang_lipengjun platform 1 broken function level authorization (by cnblogs.com)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.