Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.3amended

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

CVE-2026-79914GHSA-wrr5-j383-f7h2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nocobase/plugin-action-custom-request 2.2.0-alpha.4, 2.1.15), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary A Server-Side Request Forgery vulnerability exists in NocoBase v2.1.10 in the `@nocobase/plugin-action-custom-request` plugin. A low-privileged authenticated user can call the `customRequests:send` endpoint and override the stored request URL at runtime using `options.url`. This causes the NocoBase server to perform outbound HTTP requests to attacker-controlled or internal URLs. * Product: NocoBase * Version: v2.1.10 * Component: `@nocobase/plugin-action-custom-request` * Severity: Moderate * Required privilege: authenticated low-privileged user / member Testing was performed only in a local Docker lab environment at `http://127.0.0.1:13000`. No public NocoBase instance was tested. Lab environment: * Docker image: `nocobase/nocobase:latest-full` * Commit: `23e2bd35625439594e4757bac31d57c9e8e695b9` * Database: PostgreSQL 16 * Containers: `nocobase-lab`, `nocobase-postgres` * Docker network: `172.19.0.0/16` * Important environment variable: `SERVER_REQUEST_WHITELIST` was…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-wrr5-j383-f7h2

  2. Revision 1 · created ·

    Published from ghsa record GHSA-wrr5-j383-f7h2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-79914

Advisory: NocoBase: @nocobase/plugin-action-custom-request allows server-side request forgery through runtime URL overrides
IDs: CVE-2026-79914, GHSA-wrr5-j383-f7h2
Record: https://patchnext.com/advisories/cve-2026-79914 (revision 2, source checked 11 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @nocobase/plugin-action-custom-request 2.2.0-alpha.4, 2.1.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nocobase/plugin-action-custom-request: affected >= 2.1.0-alpha.8, < 2.1.15; >= 2.2.0-alpha.1, < 2.2.0-alpha.4; fixed in 2.2.0-alpha.4, 2.1.15

## Suggested inspection (read-only)
- `npm ls @nocobase/plugin-action-custom-request --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @nocobase/plugin-action-custom-request.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wrr5-j383-f7h2 (GitHub-reviewed advisory GHSA-wrr5-j383-f7h2 lists affected ranges: npm @nocobase/plugin-action-custom-request >=2.1.0-alpha.8 =2.2.0-alpha.1 <2.2.0-alpha.4)
- Verified: https://osv.dev/vulnerability/GHSA-wrr5-j383-f7h2 (OSV record GHSA-wrr5-j383-f7h2 lists affected ranges: npm @nocobase/plugin-action-custom-request >=2.1.0-alpha.8 =2.2.0-alpha.1 <2.2.0-alpha.4 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…