moxi624 Mogu Blog v2 up to 5.2 blogSort Endpoint info.ftl BlogSortServiceImpl.addBlogSort sortName cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 1.25+ |
Summary
A vulnerability identified as problematic has been detected in moxi624 Mogu Blog v2 up to 5.2. This vulnerability affects the function BlogSortServiceImpl.addBlogSort of the file mogu_web/src/main/resources/templates/info.ftl of the component blogSort Endpoint. This manipulation of the argument sortName causes cross site scripting.
This vulnerability appears as CVE-2026-90568. The attack may be initiated remotely. There is no available exploit.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in moxi624 Mogu Blog v2 up to 5.2. It has been declared as problematic. Affected by this vulnerability is the function BlogSortServiceImpl.addBlogSort of the file mogu_web/src/main/resources/templates/info.ftl of the component blogSort Endpoint. The manipulation of the argument sortName with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity.
The advisory is shared at gitee.com. This vulnerability is known as CVE-2026-90568. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The project was informed of the problem early through an issue report but has not responded yet.
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
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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/12/2026 Advisory disclosed09/12/2026 VulDB entry created
09/12/2026 VulDB entry last update
Sources
Advisory: IK5STWStatus: Not defined
CVE: CVE-2026-90568 (🔒)
GCVE (CVE): GCVE-0-2026-90568
GCVE (VulDB): GCVE-100-403153
Entry
Created: 09/12/2026 18:05Changes: 09/12/2026 18:05 (57)
Complete: 🔍
Submitter: JunRoinxxX
Cache ID: 216::103
Submit
Accepted
- Submit #912672: moxi624 Mogu Blog v2 V4.0 through v5.2; source through 025d78c Cross Site Scripting (by JunRoinxxX)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.