CVE-2026-52475: AiFlowy stored XSS via unrestricted file upload in UploadController

CVE-2026-52475 · Severity: info · CVSS 6.1 · Published 2026-07-21

AiFlowy, an open-source workflow or automation platform, contains a security flaw that allows unauthorized users to upload malicious files. By tricking a legitimate user into opening a specially crafted link or file hosted on the server, an attacker can steal login tokens, hijack user sessions, or perform unauthorized actions on the victim's behalf. This vulnerability does not require a password to exploit and can lead to identity theft or the spread of malware.

Technologies: AiFlowy. Vendors: AiFlowy.

Quick answers

Is CVE-2026-52475 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-52475 being exploited in the wild.
How severe is CVE-2026-52475?
Informational severity, with a CVSS score of 6.1, published 21 July 2026.
Which products and versions are affected?
AiFlowy <= 2.1.2.
Is there a fix for CVE-2026-52475?
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-52475 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-52475?
Check whether you run AiFlowy 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

A stored Cross-Site Scripting (XSS) vulnerability exists in AiFlowy versions up to and including 2.1.2. The 'UploadController.java' file, specifically the '/api/v1/commons/uploadPrePath' endpoint, fails to restrict file types and is marked with the 'SaIgnore' annotation, bypassing authentication checks. A remote, unauthenticated attacker can upload arbitrary files (such as HTML containing malicious JavaScript). Because the application serves these files from the '/static/' directory without proper content-type enforcement or sanitization, the script executes in the context of the victim's browser when accessed. This can lead to session hijacking via 'aiflowy-token' theft and unauthorized API interactions.

Affected products

  • AiFlowy AiFlowy <= 2.1.2

Timeline

  • 2026-07-21: disclosed: Initial disclosure via GitHub and NVD publication

References

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