Common Weakness Enumeration

CWE-918

Allowed

Server-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.

4652 vulnerabilities reference this CWE, most recent first.

GHSA-PVC8-V7RQ-QGMP

Vulnerability from github – Published: 2025-08-26 00:31 – Updated: 2025-08-26 00:31
VLAI
Details

A vulnerability was found in kalcaddle kodbox 1.61. Affected by this vulnerability is an unknown functionality of the file /?explorer/upload/serverDownload of the component Download from Link Handler. Performing manipulation of the argument url results in server-side request forgery. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-9414"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-08-25T19:15:32Z",
    "severity": "MODERATE"
  },
  "details": "A vulnerability was found in kalcaddle kodbox 1.61. Affected by this vulnerability is an unknown functionality of the file /?explorer/upload/serverDownload of the component Download from Link Handler. Performing manipulation of the argument url results in server-side request forgery. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.",
  "id": "GHSA-pvc8-v7rq-qgmp",
  "modified": "2025-08-26T00:31:14Z",
  "published": "2025-08-26T00:31:14Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-9414"
    },
    {
      "type": "WEB",
      "url": "https://gist.github.com/SysEternals/a03d45b582451f243f9c24076593c49c"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?ctiid.321256"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?id.321256"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?submit.633727"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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-PVCJ-PG6X-H564

Vulnerability from github – Published: 2023-10-10 03:30 – Updated: 2024-04-04 08:26
VLAI
Details

SAP NetWeaver AS Java (GRMG Heartbeat application) - version 7.50, allows an attacker to send a crafted request from a vulnerable web application, causing limited impact on confidentiality and integrity of the application.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-42477"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-10-10T02:15:11Z",
    "severity": "MODERATE"
  },
  "details": "SAP NetWeaver AS Java (GRMG Heartbeat application) - version 7.50,\u00a0allows an attacker to send a crafted request from a vulnerable web application, causing limited impact on confidentiality and integrity of the application.\n\n",
  "id": "GHSA-pvcj-pg6x-h564",
  "modified": "2024-04-04T08:26:58Z",
  "published": "2023-10-10T03:30:28Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-42477"
    },
    {
      "type": "WEB",
      "url": "https://me.sap.com/notes/3333426"
    },
    {
      "type": "WEB",
      "url": "https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-PVRG-9Q9R-H8CF

Vulnerability from github – Published: 2023-06-14 09:30 – Updated: 2023-06-14 09:30
VLAI
Details

A vulnerability, which was classified as critical, has been found in OTCMS up to 6.62. This issue affects some unknown processing of the file /admin/read.php?mudi=getSignal. The manipulation of the argument signalUrl leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-231509 was assigned to this vulnerability.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-3238"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-06-14T08:15:09Z",
    "severity": "MODERATE"
  },
  "details": "A vulnerability, which was classified as critical, has been found in OTCMS up to 6.62. This issue affects some unknown processing of the file /admin/read.php?mudi=getSignal. The manipulation of the argument signalUrl leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-231509 was assigned to this vulnerability.",
  "id": "GHSA-pvrg-9q9r-h8cf",
  "modified": "2023-06-14T09:30:42Z",
  "published": "2023-06-14T09:30:42Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3238"
    },
    {
      "type": "WEB",
      "url": "https://github.com/HuBenLab/HuBenVulList/blob/main/OTCMS%20is%20vulnerable%20to%20Server-side%20request%20forgery%20(SSRF).md"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?ctiid.231509"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?id.231509"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-PVRJ-8CG3-J5F8

Vulnerability from github – Published: 2026-07-01 18:16 – Updated: 2026-07-01 18:16
VLAI
Summary
auth-fetch-mcp has SSRF Protection Bypass via IPv4-mapped IPv6 Loopback
Details

SSRF Protection Bypass via IPv4-mapped IPv6 Loopback

Summary

auth-fetch-mcp v3.0.1 implements SSRF protection in assertSafeUrl() (src/security.ts) to block requests to private and loopback addresses. However, the isPrivateV6() function fails to detect IPv4-mapped IPv6 loopback addresses in their hex-normalized form. When an attacker supplies a URL such as http://[::ffff:127.0.0.1]:PORT/, the Node.js WHATWG URL parser silently normalizes the host to [::ffff:7f00:1]. Because net.isIPv4('7f00:1') returns false, the private-IP check is bypassed and the URL is passed to the browser or HTTP client, allowing the MCP tool to reach loopback services that are supposed to be blocked. The issue is exploitable under default configuration without any special environment variable and carries a CVSS v3.1 Base Score of 7.4 (High).

Details

The vulnerable function is isPrivateV6() in src/security.ts, called from assertSafeUrl() which gates every outbound request made by the auth_fetch and download_media MCP tools.

Root cause — src/security.ts:46-50:

if (lower.startsWith("::ffff:")) {
  const v4 = lower.slice(7);          // "7f00:1" after Node normalization
  if (net.isIPv4(v4)) return isPrivateV4(v4);  // false → falls through
}
return false;   // loopback escapes the guard

The Node.js WHATWG URL class (conforming to the URL Living Standard) hex-normalizes IPv4-mapped IPv6 addresses:

Input hostname After new URL(...).hostname
::ffff:127.0.0.1 ::ffff:7f00:1
::ffff:192.168.1.1 ::ffff:c0a8:101

After normalization, the suffix after ::ffff: is no longer a dotted-decimal IPv4 string, so net.isIPv4() returns false. The guard falls through and isPrivateV6() returns false, causing assertSafeUrl() to treat a loopback address as safe.

Data flow — primary sink (auth_fetch):

  1. src/tools.ts:119auth_fetch accepts user-controlled url: z.string() (source).
  2. src/tools.ts:128-131 — handler calls navigateTo(ctx, url), passing the raw URL.
  3. src/browser.ts:58navigateTo() calls assertSafeUrl(url).
  4. src/security.ts:74-108assertSafeUrl() delegates IPv6 host validation to isPrivateV6(); hex-normalized loopback bypasses the check.
  5. src/browser.ts:66page.goto(safeUrl.toString()) issues a browser request to the internal address.
  6. src/extractor.ts:33-54 / src/tools.ts:171-176 — page content is extracted and returned to the MCP caller.

Data flow — secondary sink (download_media):

  1. src/tools.ts:198-210download_media accepts user-controlled urls[].
  2. src/tools.ts:233-234 — each URL passes through assertSafeUrl() then ctx.request.get(safeUrl.toString()).
  3. src/tools.ts:253-254 — the response body is written to the local downloads directory and the path is returned.

Dynamic confirmation (Phase 2):

The PoC ran inside a Docker container (--network=host). Direct loopback URLs are correctly blocked:

[BASELINE-BLOCK] Refusing to fetch 127.0.0.1 (resolves to private/loopback/link-local address 127.0.0.1)
[BASELINE-BLOCK] Refusing to fetch [::1] (resolves to private/loopback/link-local address ::1)

The IPv4-mapped IPv6 form bypasses the check and reaches the internal service:

[VULN] SECURITY_BYPASS: assertSafeUrl() did not throw
[VULN] Input URL:       http://[::ffff:127.0.0.1]:31337/
[VULN] Normalized URL:  http://[::ffff:7f00:1]:31337/
[VULN] Cause: net.isIPv4('7f00:1') = false → isPrivateV6() returns false
[SSRF] HTTP response received from internal service
[CONFIRMED] SSRF_CONFIRMED: response contains INTERNAL_SECRET_MARKER
[CONFIRMED] VULNERABILITY_REPRODUCED=TRUE

PoC

Prerequisites:

git clone https://github.com/ymw0407/auth-fetch-mcp.git
cd auth-fetch-mcp
npm ci
npm run build
npx playwright install --with-deps chromium

Terminal 1 — start a loopback-only internal service:

node -e 'require("http").createServer((q,r)=>r.end("<h1>INTERNAL_SECRET_MARKER</h1>")).listen(31337,"127.0.0.1")'

Terminal 2 — start the MCP server (default config, no special env vars):

npx auth-fetch-mcp@3.0.1

MCP tool invocation:

{
  "tool": "auth_fetch",
  "arguments": {
    "url": "http://[::ffff:127.0.0.1]:31337/"
  }
}

Expected vs. actual behavior:

URL Expected Actual
http://127.0.0.1:31337/ BLOCK BLOCK (correct)
http://[::1]:31337/ BLOCK BLOCK (correct)
http://[::ffff:127.0.0.1]:31337/ BLOCK ALLOW (vulnerable)
http://[::ffff:7f00:1]:31337/ BLOCK ALLOW (vulnerable)

After the user clicks the "Capture" button, the MCP response contains INTERNAL_SECRET_MARKER, confirming that the internal HTTP service was reached through the SSRF protection bypass.

Remediation

Decode the hex-encoded IPv4-mapped suffix before passing it to isPrivateV4():

 if (lower.startsWith("::ffff:")) {
   const v4 = lower.slice(7);
   if (net.isIPv4(v4)) return isPrivateV4(v4);
+  const m = /^([0-9a-f]{1,4}):([0-9a-f]{1,4})$/.exec(v4);
+  if (m) {
+    const hi = parseInt(m[1], 16);
+    const lo = parseInt(m[2], 16);
+    const mapped = `${hi >> 8}.${hi & 255}.${lo >> 8}.${lo & 255}`;
+    return isPrivateV4(mapped);
+  }
 }

Additionally, a BrowserContext route guard should be added in src/browser.ts to re-validate every navigation URL (including redirect targets) through assertSafeUrl().

No patched version available.

Impact

This is a Server-Side Request Forgery (SSRF) vulnerability. An attacker who can supply or influence the url argument of the auth_fetch tool (or the urls[] array of download_media) can direct the MCP server to make HTTP requests to services bound to 127.0.0.1 or any other private IPv4 range, simply by encoding the target address as an IPv4-mapped IPv6 literal.

Who is impacted:

  • End users running auth-fetch-mcp locally: an attacker who can inject tool arguments (e.g., via a prompt-injection payload in a webpage visited by the AI agent) can read the response from any HTTP service on the user's loopback interface — local dev servers, admin panels, credential endpoints, metadata services, or other MCP servers.
  • Server-side deployments: any deployment exposing auth-fetch-mcp as a shared MCP server faces the same risk against internal network services reachable from the host.
  • The auth_fetch UI:R capture step is reflected in the CVSS score but does not eliminate the risk in prompt-injection scenarios, which the product's README explicitly identifies as an intended protection boundary.

Confidentiality of internal service responses is fully compromised (C:H); integrity and availability of the target service are not directly affected by this issue.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 3.0.1"
      },
      "package": {
        "ecosystem": "npm",
        "name": "auth-fetch-mcp"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-49857"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-01T18:16:22Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "## SSRF Protection Bypass via IPv4-mapped IPv6 Loopback\n\n### Summary\n\n`auth-fetch-mcp` v3.0.1 implements SSRF protection in `assertSafeUrl()` (`src/security.ts`) to block requests to private and loopback addresses. However, the `isPrivateV6()` function fails to detect IPv4-mapped IPv6 loopback addresses in their hex-normalized form. When an attacker supplies a URL such as `http://[::ffff:127.0.0.1]:PORT/`, the Node.js WHATWG URL parser silently normalizes the host to `[::ffff:7f00:1]`. Because `net.isIPv4(\u00277f00:1\u0027)` returns `false`, the private-IP check is bypassed and the URL is passed to the browser or HTTP client, allowing the MCP tool to reach loopback services that are supposed to be blocked. The issue is exploitable under default configuration without any special environment variable and carries a CVSS v3.1 Base Score of **7.4 (High)**.\n\n### Details\n\nThe vulnerable function is `isPrivateV6()` in `src/security.ts`, called from `assertSafeUrl()` which gates every outbound request made by the `auth_fetch` and `download_media` MCP tools.\n\n**Root cause \u2014 `src/security.ts:46-50`:**\n\n```ts\nif (lower.startsWith(\"::ffff:\")) {\n  const v4 = lower.slice(7);          // \"7f00:1\" after Node normalization\n  if (net.isIPv4(v4)) return isPrivateV4(v4);  // false \u2192 falls through\n}\nreturn false;   // loopback escapes the guard\n```\n\nThe Node.js WHATWG URL class (conforming to the URL Living Standard) hex-normalizes IPv4-mapped IPv6 addresses:\n\n| Input hostname | After `new URL(...).hostname` |\n|---|---|\n| `::ffff:127.0.0.1` | `::ffff:7f00:1` |\n| `::ffff:192.168.1.1` | `::ffff:c0a8:101` |\n\nAfter normalization, the suffix after `::ffff:` is no longer a dotted-decimal IPv4 string, so `net.isIPv4()` returns `false`. The guard falls through and `isPrivateV6()` returns `false`, causing `assertSafeUrl()` to treat a loopback address as safe.\n\n**Data flow \u2014 primary sink (`auth_fetch`):**\n\n1. `src/tools.ts:119` \u2014 `auth_fetch` accepts user-controlled `url: z.string()` (source).\n2. `src/tools.ts:128-131` \u2014 handler calls `navigateTo(ctx, url)`, passing the raw URL.\n3. `src/browser.ts:58` \u2014 `navigateTo()` calls `assertSafeUrl(url)`.\n4. `src/security.ts:74-108` \u2014 `assertSafeUrl()` delegates IPv6 host validation to `isPrivateV6()`; hex-normalized loopback bypasses the check.\n5. `src/browser.ts:66` \u2014 `page.goto(safeUrl.toString())` issues a browser request to the internal address.\n6. `src/extractor.ts:33-54` / `src/tools.ts:171-176` \u2014 page content is extracted and returned to the MCP caller.\n\n**Data flow \u2014 secondary sink (`download_media`):**\n\n1. `src/tools.ts:198-210` \u2014 `download_media` accepts user-controlled `urls[]`.\n2. `src/tools.ts:233-234` \u2014 each URL passes through `assertSafeUrl()` then `ctx.request.get(safeUrl.toString())`.\n3. `src/tools.ts:253-254` \u2014 the response body is written to the local downloads directory and the path is returned.\n\n**Dynamic confirmation (Phase 2):**\n\nThe PoC ran inside a Docker container (`--network=host`). Direct loopback URLs are correctly blocked:\n\n```\n[BASELINE-BLOCK] Refusing to fetch 127.0.0.1 (resolves to private/loopback/link-local address 127.0.0.1)\n[BASELINE-BLOCK] Refusing to fetch [::1] (resolves to private/loopback/link-local address ::1)\n```\n\nThe IPv4-mapped IPv6 form bypasses the check and reaches the internal service:\n\n```\n[VULN] SECURITY_BYPASS: assertSafeUrl() did not throw\n[VULN] Input URL:       http://[::ffff:127.0.0.1]:31337/\n[VULN] Normalized URL:  http://[::ffff:7f00:1]:31337/\n[VULN] Cause: net.isIPv4(\u00277f00:1\u0027) = false \u2192 isPrivateV6() returns false\n[SSRF] HTTP response received from internal service\n[CONFIRMED] SSRF_CONFIRMED: response contains INTERNAL_SECRET_MARKER\n[CONFIRMED] VULNERABILITY_REPRODUCED=TRUE\n```\n\n### PoC\n\n**Prerequisites:**\n\n```bash\ngit clone https://github.com/ymw0407/auth-fetch-mcp.git\ncd auth-fetch-mcp\nnpm ci\nnpm run build\nnpx playwright install --with-deps chromium\n```\n\n**Terminal 1 \u2014 start a loopback-only internal service:**\n\n```bash\nnode -e \u0027require(\"http\").createServer((q,r)=\u003er.end(\"\u003ch1\u003eINTERNAL_SECRET_MARKER\u003c/h1\u003e\")).listen(31337,\"127.0.0.1\")\u0027\n```\n\n**Terminal 2 \u2014 start the MCP server (default config, no special env vars):**\n\n```bash\nnpx auth-fetch-mcp@3.0.1\n```\n\n**MCP tool invocation:**\n\n```json\n{\n  \"tool\": \"auth_fetch\",\n  \"arguments\": {\n    \"url\": \"http://[::ffff:127.0.0.1]:31337/\"\n  }\n}\n```\n\n**Expected vs. actual behavior:**\n\n| URL | Expected | Actual |\n|---|---|---|\n| `http://127.0.0.1:31337/` | BLOCK | BLOCK (correct) |\n| `http://[::1]:31337/` | BLOCK | BLOCK (correct) |\n| `http://[::ffff:127.0.0.1]:31337/` | BLOCK | **ALLOW** (vulnerable) |\n| `http://[::ffff:7f00:1]:31337/` | BLOCK | **ALLOW** (vulnerable) |\n\nAfter the user clicks the \"Capture\" button, the MCP response contains `INTERNAL_SECRET_MARKER`, confirming that the internal HTTP service was reached through the SSRF protection bypass.\n\n### Remediation\n\nDecode the hex-encoded IPv4-mapped suffix before passing it to `isPrivateV4()`:\n\n```diff\n if (lower.startsWith(\"::ffff:\")) {\n   const v4 = lower.slice(7);\n   if (net.isIPv4(v4)) return isPrivateV4(v4);\n+  const m = /^([0-9a-f]{1,4}):([0-9a-f]{1,4})$/.exec(v4);\n+  if (m) {\n+    const hi = parseInt(m[1], 16);\n+    const lo = parseInt(m[2], 16);\n+    const mapped = `${hi \u003e\u003e 8}.${hi \u0026 255}.${lo \u003e\u003e 8}.${lo \u0026 255}`;\n+    return isPrivateV4(mapped);\n+  }\n }\n```\n\nAdditionally, a `BrowserContext` route guard should be added in `src/browser.ts` to re-validate every navigation URL (including redirect targets) through `assertSafeUrl()`.\n\nNo patched version available.\n\n### Impact\n\nThis is a **Server-Side Request Forgery (SSRF)** vulnerability. An attacker who can supply or influence the `url` argument of the `auth_fetch` tool (or the `urls[]` array of `download_media`) can direct the MCP server to make HTTP requests to services bound to `127.0.0.1` or any other private IPv4 range, simply by encoding the target address as an IPv4-mapped IPv6 literal.\n\n**Who is impacted:**\n\n- **End users** running `auth-fetch-mcp` locally: an attacker who can inject tool arguments (e.g., via a prompt-injection payload in a webpage visited by the AI agent) can read the response from any HTTP service on the user\u0027s loopback interface \u2014 local dev servers, admin panels, credential endpoints, metadata services, or other MCP servers.\n- **Server-side deployments**: any deployment exposing `auth-fetch-mcp` as a shared MCP server faces the same risk against internal network services reachable from the host.\n- The `auth_fetch` UI:R capture step is reflected in the CVSS score but does not eliminate the risk in prompt-injection scenarios, which the product\u0027s README explicitly identifies as an intended protection boundary.\n\nConfidentiality of internal service responses is fully compromised (C:H); integrity and availability of the target service are not directly affected by this issue.",
  "id": "GHSA-pvrj-8cg3-j5f8",
  "modified": "2026-07-01T18:16:22Z",
  "published": "2026-07-01T18:16:22Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ymw0407/auth-fetch-mcp/security/advisories/GHSA-pvrj-8cg3-j5f8"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ymw0407/auth-fetch-mcp"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "auth-fetch-mcp has SSRF Protection Bypass via IPv4-mapped IPv6 Loopback"
}

GHSA-PVRP-6FJQ-X9RJ

Vulnerability from github – Published: 2025-03-20 15:30 – Updated: 2025-03-24 15:30
VLAI
Details

Inflectra SpiraTeam 7.2.00 is vulnerable to Server-Side Request Forgery (SSRF) via the NewsReaderService. This allows an attacker to escalate privileges and obtain sensitive information.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-48590"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-03-20T14:15:20Z",
    "severity": "CRITICAL"
  },
  "details": "Inflectra SpiraTeam 7.2.00 is vulnerable to Server-Side Request Forgery (SSRF) via the NewsReaderService. This allows an attacker to escalate privileges and obtain sensitive information.",
  "id": "GHSA-pvrp-6fjq-x9rj",
  "modified": "2025-03-24T15:30:39Z",
  "published": "2025-03-20T15:30:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-48590"
    },
    {
      "type": "WEB",
      "url": "https://github.com/GCatt-AS/CVE-2024-48590/blob/main/README.md"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-PW25-C82R-75MM

Vulnerability from github – Published: 2025-08-25 21:48 – Updated: 2025-08-26 17:12
VLAI
Summary
request-filtering-agent SSRF Bypass via HTTPS Requests to 127.0.0.1
Details

request-filtering-agent versions 1.x.x and earlier contain a vulnerability where HTTPS requests to 127.0.0.1 bypass IP address filtering, while HTTP requests are correctly blocked.

Impact:

Vulnerable patterns (requests that should be blocked but are allowed): - https://127.0.0.1:443/api - https://127.0.0.1:8443/admin - Any HTTPS request using direct IP address https://127.0.0.1

This vulnerability primarily affects services using self-signed certificates on 127.0.0.1.

Not affected (correctly blocked in all versions): - http://127.0.0.1:80/api - HTTP requests are properly blocked - https://localhost:443/api - Domain-based requests trigger DNS lookup and are blocked - http://localhost:80/api - Domain-based HTTP requests are blocked - Requests to other private IPs like 192.168.x.x, 10.x.x.x, 172.16.x.x

This allows attackers to potentially access internal HTTPS services running on localhost, bypassing the library's SSRF protection. The vulnerability is particularly dangerous when the application accepts user-controlled URLs and internal services are only protected by network-level restrictions.

Fixed in 2.0.0

This vulnerability has been fixed in request-filtering-agent version 2.0.0. Users should upgrade to version 2.0.0 or later.

Root Cause:The HTTPS agent fails to validate direct IP addresses like https://127.0.0.1 during TLS connection setup, allowing them to bypass the security filter.

Details: https://github.com/azu/request-filtering-agent-https127-test

Thanks Luca

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "request-filtering-agent"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-57814"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-08-25T21:48:01Z",
    "nvd_published_at": "2025-08-25T22:15:33Z",
    "severity": "MODERATE"
  },
  "details": "request-filtering-agent versions 1.x.x and earlier contain a vulnerability where HTTPS requests to 127.0.0.1 bypass IP address filtering, while HTTP requests are correctly blocked.\n\n**Impact:**\n\nVulnerable patterns (requests that should be blocked but are allowed):\n- https://127.0.0.1:443/api\n- https://127.0.0.1:8443/admin\n- Any HTTPS request using direct IP address `https://127.0.0.1`\n\nThis vulnerability primarily affects services using self-signed certificates on `127.0.0.1`.\n\n**Not affected (correctly blocked in all versions):**\n- http://127.0.0.1:80/api - HTTP requests are properly blocked\n- https://localhost:443/api - Domain-based requests trigger DNS lookup and are blocked\n- http://localhost:80/api - Domain-based HTTP requests are blocked\n- Requests to other private IPs like 192.168.x.x, 10.x.x.x, 172.16.x.x\n\nThis allows attackers to potentially access internal HTTPS services running on localhost, bypassing the library\u0027s SSRF protection. The vulnerability is particularly dangerous when the application accepts user-controlled URLs and internal services are only protected by network-level restrictions.\n\n## Fixed in 2.0.0\n\nThis vulnerability has been fixed in request-filtering-agent version 2.0.0. Users should upgrade to version 2.0.0 or later.\n\nRoot Cause:The HTTPS agent fails to validate direct IP addresses like `https://127.0.0.1` during TLS connection setup, allowing them to bypass the security filter.\n\nDetails: https://github.com/azu/request-filtering-agent-https127-test\n\nThanks Luca",
  "id": "GHSA-pw25-c82r-75mm",
  "modified": "2025-08-26T17:12:50Z",
  "published": "2025-08-25T21:48:01Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/azu/request-filtering-agent/security/advisories/GHSA-pw25-c82r-75mm"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-57814"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/azu/request-filtering-agent"
    },
    {
      "type": "WEB",
      "url": "https://github.com/azu/request-filtering-agent-https127-test"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P",
      "type": "CVSS_V4"
    }
  ],
  "summary": "request-filtering-agent SSRF Bypass via HTTPS Requests to 127.0.0.1"
}

GHSA-PW64-6V6V-94VP

Vulnerability from github – Published: 2023-01-23 15:30 – Updated: 2025-04-02 18:30
VLAI
Details

ONLYOFFICE all versions as of 2021-11-08 is vulnerable to Server-Side Request Forgery (SSRF). The document editor service can be abused to read and serve arbitrary URLs as a document.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2021-43449"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-01-23T15:15:00Z",
    "severity": "HIGH"
  },
  "details": "ONLYOFFICE all versions as of 2021-11-08 is vulnerable to Server-Side Request Forgery (SSRF). The document editor service can be abused to read and serve arbitrary URLs as a document.",
  "id": "GHSA-pw64-6v6v-94vp",
  "modified": "2025-04-02T18:30:39Z",
  "published": "2023-01-23T15:30:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-43449"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ONLYOFFICE/server"
    },
    {
      "type": "WEB",
      "url": "https://labs.nettitude.com/blog/exploiting-onlyoffice-web-sockets-for-unauthenticated-remote-code-execution"
    },
    {
      "type": "WEB",
      "url": "https://www.onlyoffice.com"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-PW72-XM42-HR32

Vulnerability from github – Published: 2022-02-10 00:00 – Updated: 2022-02-10 00:00
VLAI
Details

The OIDC OP plugin before 3.0.4 for Shibboleth Identity Provider allows server-side request forgery (SSRF) due to insufficient restriction of the request_uri parameter. This allows attackers to interact with arbitrary third-party HTTP services.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2022-24129"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2022-02-04T20:15:00Z",
    "severity": "HIGH"
  },
  "details": "The OIDC OP plugin before 3.0.4 for Shibboleth Identity Provider allows server-side request forgery (SSRF) due to insufficient restriction of the request_uri parameter. This allows attackers to interact with arbitrary third-party HTTP services.",
  "id": "GHSA-pw72-xm42-hr32",
  "modified": "2022-02-10T00:00:50Z",
  "published": "2022-02-10T00:00:50Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-24129"
    },
    {
      "type": "WEB",
      "url": "https://github.com/sbaresearch/advisories/tree/public/2022/SBA-ADV-20220127-01_Shibboleth_IdP_OIDC_OP_Plugin_SSRF"
    },
    {
      "type": "WEB",
      "url": "http://shibboleth.net/community/advisories"
    },
    {
      "type": "WEB",
      "url": "http://shibboleth.net/community/advisories/secadv_20220131.txt"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-PW8X-CFHF-JJH6

Vulnerability from github – Published: 2022-06-22 00:00 – Updated: 2022-06-29 00:00
VLAI
Details

The GeoAnalytics feature in Qlik Sense April 2020 patch 4 allows SSRF.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2021-36761"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2022-06-21T17:15:00Z",
    "severity": "MODERATE"
  },
  "details": "The GeoAnalytics feature in Qlik Sense April 2020 patch 4 allows SSRF.",
  "id": "GHSA-pw8x-cfhf-jjh6",
  "modified": "2022-06-29T00:00:25Z",
  "published": "2022-06-22T00:00:53Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-36761"
    },
    {
      "type": "WEB",
      "url": "https://www.cyberiskvision.com/advisory"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-PWM7-WR54-2JXV

Vulnerability from github – Published: 2026-04-02 09:30 – Updated: 2026-04-02 09:30
VLAI
Details

The Webmention plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 5.6.2 in the 'MF2::parse_authorpage' function via the 'Receiver::post' function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-0686"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-04-02T08:16:27Z",
    "severity": "HIGH"
  },
  "details": "The Webmention plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 5.6.2 in the \u0027MF2::parse_authorpage\u0027 function via the \u0027Receiver::post\u0027 function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.",
  "id": "GHSA-pwm7-wr54-2jxv",
  "modified": "2026-04-02T09:30:24Z",
  "published": "2026-04-02T09:30:24Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0686"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pfefferle/wordpress-webmention/blob/057223cee18a9e93b017d0f21db6ea77a7686489/includes/handler/class-mf2.php#L878"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/webmention/tags/5.6.2/includes/class-receiver.php#L260"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/webmention/tags/5.6.2/includes/handler/class-mf2.php#L877"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset/3494831/webmention"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/08d15c46-d15f-4803-80be-90bf33335c18?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

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.