# CVE-2026-90568: moxi624 Mogu Blog v2 blogSort Endpoint info.ftl BlogSortServiceImpl.addBlogSort cross site scripting

> Remote attackers can inject malicious scripts via the sortName parameter in the blogSort endpoint, potentially compromising user sessions.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-4jph-rgqm-gxcv

## What is CVE-2026-90568?

CVE-2026-90568 is a medium-severity cross-site scripting vulnerability in moxi624 Mogu Blog v2, published on 13 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was detected in moxi624 Mogu Blog v2 up to 5.2. This affects 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 results in cross site scripting. The attack can be launched remotely. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-90568?


## How do I fix CVE-2026-90568?

No fix has been published for CVE-2026-90568 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90568 being exploited?

There is no known exploitation of CVE-2026-90568 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90568 and fix it if it is affected.

What it is: CVE-2026-90568 is a medium-severity cross-site scripting vulnerability in moxi624 Mogu Blog v2, published on 13 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-90568 in the wild and no public exploit code.

Affected product: moxi624 Mogu Blog v2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90568/ (Markdown: https://insights.sbomify.com/CVE-2026-90568/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90568
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90568
- OSV: https://osv.dev/vulnerability/CVE-2026-90568

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90568/
Summaries are generated and may contain mistakes; the official description above is the record.