Quick answers
- Is CVE-2026-90527 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90527 being exploited in the wild.
- How severe is CVE-2026-90527?
- Medium severity, with a CVSS score of 4.3, published 13 September 2026.
- Which products and versions are affected?
- Quequnlong Shiyi-Blog 1.0.0 to 1.2.1.
- Is there a fix for CVE-2026-90527?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-90527 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-90527?
- Check whether you run Quequnlong Shiyi-Blog at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stored XSS in the message submission API endpoint (`POST /api/message/add`). Unauthenticated attackers can submit malicious HTML/JavaScript in the `body.content` parameter. The backend applies only basic sensitive-word filtering before storing the content in the database. When administrators access the message management page in the admin dashboard, the frontend renders the stored content using Vue's `v-html` directive without sanitization, executing the attacker's script in the admin's browser context. The `/api/**` endpoints are explicitly excluded from Sa-Token authentication checks, so no credentials are required. Attack success depends on an admin viewing the messages page.
Affected products
- quequnlong shiyi-blog 1.0.0 to 1.2.1
Timeline
- 2026-08-01: disclosed: Vulnerability reported via Gitee issue IK5RF6
- 2026-09-13: advisory: CVE-2026-90527 published