Is CVE-2026-90568 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-90568 being exploited in the wild.

How severe is CVE-2026-90568?

Low severity, with a CVSS score of 3.5, published 13 September 2026.

Which products and versions are affected?

moxi624 Mogu Blog v4.0 through v5.2.

Is there a fix for CVE-2026-90568?

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-90568 attacked?

It is attacked over the network.

Am I affected by CVE-2026-90568?

Check whether anything you run is named in the advisory. 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.

CVE-2026-90568: moxi624 Mogu Blog stored XSS in blog category name

CVE-2026-90568 · Severity: low · CVSS 3.5 · Published 2026-09-13

Mogu Blog is an open-source blog platform. A stored cross-site scripting (XSS) vulnerability allows authenticated users with blog category management permissions to inject malicious scripts into category names. When other users view articles in the affected category, the injected script executes in their browser, potentially stealing session tokens, redirecting users to malicious sites, or defacing content.

Quick answers

Is CVE-2026-90568 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-90568 being exploited in the wild.
How severe is CVE-2026-90568?: Low severity, with a CVSS score of 3.5, published 13 September 2026.
Which products and versions are affected?: moxi624 Mogu Blog v4.0 through v5.2.
Is there a fix for CVE-2026-90568?: 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-90568 attacked?: It is attacked over the network.
Am I affected by CVE-2026-90568?: Check whether anything you run is named in the advisory. 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

This is a stored (persistent) cross-site scripting vulnerability in the blog category name field (BlogSort.sortName). The vulnerability exists in the BlogSortServiceImpl.addBlogSort and editBlogSort methods, which fail to sanitize or HTML-encode the sortName parameter before persisting it to the database. The vulnerable data is then rendered without escaping in the Freemarker template (mogu_web/src/main/resources/templates/info.ftl at lines 43 and 51) on the public-facing article detail page. An authenticated backend user with category management permissions (not necessarily a superadmin) can inject arbitrary HTML/JavaScript through the /blogSort/add or /blogSort/edit endpoints. Any visitor subsequently viewing an article in the affected category will trigger the malicious script execution in their browser context. The vulnerability affects versions 4.0 through 5.2 and the current source code.

Affected products

moxi624 Mogu Blog v4.0 through v5.2

Timeline

2026-08-01: disclosed: Vulnerability reported via Gitee issue #IK5STW
2026-09-13: advisory: CVE-2026-90568 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.