quequnlong shiyi-blog 1.0.0-1.2.1 chat sendMsg Endpoint index.vue SysChatMsgMapper.getChatMsgList chat_msg cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 2.73+ |
Summary
A vulnerability was found in quequnlong shiyi-blog 1.0.0-1.2.1. It has been classified as problematic. Affected is the function SysChatMsgMapper.getChatMsgList of the file blog-web/src/views/chat/index.vue of the component chat sendMsg Endpoint. Performing a manipulation of the argument chat_msg results in cross site scripting.
This vulnerability is cataloged as CVE-2026-90564. It is possible to initiate the attack remotely. There is no exploit available.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability, which was classified as problematic, was found in quequnlong shiyi-blog 1.0.0-1.2.1. This affects the function SysChatMsgMapper.getChatMsgList of the file blog-web/src/views/chat/index.vue of the component chat sendMsg Endpoint. The manipulation of the argument chat_msg with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity.
The advisory is shared at gitee.com. This vulnerability is uniquely identified as CVE-2026-90564. The exploitability is told to be easy. It is possible to initiate the attack 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
Website
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
Product: gitee.comAdvisory: IK5RVL
Status: Not defined
CVE: CVE-2026-90564 (🔒)
GCVE (CVE): GCVE-0-2026-90564
GCVE (VulDB): GCVE-100-403149
Entry
Created: 09/12/2026 17:53Changes: 09/12/2026 17:53 (56)
Complete: 🔍
Submitter: JunRoinxxX
Cache ID: 216::103
Submit
Accepted
- Submit #912553: quequnlong shiyi-blog 1.0.0 through 1.2.1; source through 4db96f9 Cross Site Scripting (by JunRoinxxX)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.