CVE-2026-79914VulnerabilityPublished 10 Nov 2026

NocoBase: @nocobase/plugin-action-custom-request allows server-side request forgery through runtime URL overrides

Affects @nocobase/plugin-action-custom-requestSource GCVE Database

Compare

Authoritative record:CVE-2026-79914· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.1.15 when convenient.

Data as of 10 Nov 2026, 22:08 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	4.3

Patch: Available – fixed in 2.1.15, 2.2.0-alpha.4

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade @nocobase/plugin-action-custom-request to 2.1.15; @nocobase/plugin-action-custom-request to 2.2.0-alpha.4.

Affected software

Product	Affected	Fixed in
npm@nocobase/plugin-action-custom-request	Affected >=2.1.0-alpha.8 <2.1.15	Fixed in 2.1.15
npm@nocobase/plugin-action-custom-request	Affected >=2.2.0-alpha.1 <2.2.0-alpha.4	Fixed in 2.2.0-alpha.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading to NocoBase versions 2.1.15 or later, or 2.2.0-alpha.4 or later, where this vulnerability is fixed. Additionally, ensure the SERVER_REQUEST_WHITELIST environment variable is properly configured to restrict allowed outbound URLs. No other mitigation is required once patched or whitelist is enforced.

Description

NocoBase version 2.1.10 and certain alpha releases of 2.2.0 contain a Server-Side Request Forgery (SSRF) vulnerability in the @nocobase/plugin-action-custom-request plugin. A low-privileged authenticated user can override the stored request URL at runtime via the customRequests:send endpoint, causing the server to make arbitrary HTTP requests to attacker-controlled or internal URLs. This occurs if the SERVER_REQUEST_WHITELIST environment variable is not set, bypassing whitelist checks. The vulnerability has a moderate severity with a CVSS score of 4.3. Fixed versions include 2.1.15 and 2.2.0-alpha.4.

Impact

An attacker with low-privileged authenticated access can exploit this vulnerability to make the NocoBase server perform arbitrary HTTP requests. This can lead to unauthorized internal network scanning or interaction with internal services not otherwise accessible externally. The confidentiality impact is low as the vulnerability does not directly disclose data, and there is no integrity or availability impact reported.

Summary

The SSRF vulnerability in NocoBase arises from the ability of a low-privileged authenticated user to call the customRequests:send API endpoint and override the stored request URL using the options.url parameter at runtime. The plugin merges runtime options with stored request configurations without enforcing URL restrictions if the SERVER_REQUEST_WHITELIST environment variable is unset or empty. This allows the server to perform outbound HTTP requests to arbitrary URLs controlled by an attacker or internal network services. The vulnerability affects NocoBase versions >=2.1.0-alpha.8 and <2.1.15, and >=2.2.0-alpha.1 and <2.2.0-alpha.4. The issue is patched in versions 2.1.15 and 2.2.0-alpha.4.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 22:08 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats