Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Informational severity, with a CVSS score of 8.8, published 20 August 2026.

Which products and versions are affected?

Nocobase <2.1.5; @nocobase/server (npm) SEMVER:introduced=0,fixed=2.1.5.

Is there a fix for This vulnerability?

Yes. @nocobase/server (npm): upgrade to 2.1.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network.

Check whether you run Nocobase or @nocobase/server (npm) 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.

NocoBase arbitrary file write and local file inclusion leading to remote code execution

Q: Which products and versions are affected?

Nocobase <2.1.5; @nocobase/server (npm) SEMVER:introduced=0,fixed=2.1.5.

Q: Is there a fix for This vulnerability?

Yes. @nocobase/server (npm): upgrade to 2.1.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network.

Q: Am I affected?

Check whether you run Nocobase or @nocobase/server (npm) 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.

Severity: info · CVSS 8.8 · Published 2026-08-20

NocoBase is an open-source data management and workflow platform. Two chained vulnerabilities allow an authenticated administrator to write malicious files to arbitrary locations on disk and then execute them as code, resulting in complete server compromise. This requires valid admin credentials but leads to full remote code execution with the privileges of the NocoBase process.

Technologies: Nocobase. Vendors: NocoBase, npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Informational severity, with a CVSS score of 8.8, published 20 August 2026.
Which products and versions are affected?: Nocobase <2.1.5; @nocobase/server (npm) SEMVER:introduced=0,fixed=2.1.5.
Is there a fix for This vulnerability?: Yes. @nocobase/server (npm): upgrade to 2.1.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network.
Am I affected?: Check whether you run Nocobase or @nocobase/server (npm) 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.

How to fix

@nocobase/server (npm): upgrade to 2.1.5 or later
```
npm install @nocobase/server@2.1.5
```

Technical details

The vulnerability chain consists of two flaws: (1) The storages:update API endpoint fails to validate the documentRoot parameter, allowing an authenticated admin to redirect the file upload storage root to any absolute filesystem path, including the application directory. An upload to this redirected root then writes a malicious payload anywhere the Node.js process can write. (2) The pm:enable plugin manager endpoint passes user-supplied paths directly to Node.js require() without validation, enabling local file inclusion. By uploading a malicious JavaScript file via the redirected storage and then triggering require() on its path, an attacker executes arbitrary code. Both vulnerabilities require admin authentication, and a working proof-of-concept exploit chain has been demonstrated. Patches are available in version 2.1.5 and later.

Affected products

NocoBase NocoBase <2.1.5

Timeline

2026-06-15: disclosed
2026-06-15: patched: Fixed in version 2.1.5

References

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