Quick answers
- Is CVE-2026-84701 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84701 being exploited in the wild.
- How severe is CVE-2026-84701?
- Medium severity, with a CVSS score of 5.4, published 2 September 2026.
- Which products and versions are affected?
- Nocobase 2.2.5 and earlier.
- Is there a fix for CVE-2026-84701?
- 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-84701 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-84701?
- Check whether you run Nocobase 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
This is a stored cross-site scripting (XSS) vulnerability in the rich text field renderer (ReadPretty.tsx component). The root cause is insufficient HTML sanitization in the read renderer when displaying user-supplied rich text content. An attacker with create permissions can inject arbitrary HTML markup including event handlers via the collection API. The malicious payload is stored in the database and executed when any user views the affected record in their browser. No authentication bypass is required beyond the initial create permission. Patches are expected in subsequent releases addressing input validation on the collection API side and output encoding in the renderer.
Affected products
- NocoBase NocoBase 2.2.5 and earlier
Timeline
- 2026-09-02: disclosed
- 2026-09-02: advisory: CVE-2026-84701 published