Monthly
Authenticated blind server-side request forgery in Tandoor Recipes before 2.6.10 allows a user with privileges to create a Space and configure an AI provider URL to force the server to connect to arbitrary internal addresses. The AI actions behind TARGET/api/ai-import/ and api/ai-step-sort/ pass the attacker-supplied provider URL straight to LiteLLM, bypassing the application's safe_request outbound filtering, and the resulting connection success, refusal, or timeout is surfaced as a reachability oracle that can be used to map internal hosts, ports, and cloud metadata endpoints. Exploitation requires an authenticated account (PR:L) and the AI provider feature to be in use, and exposure is limited to a blind oracle rather than confirmed response-body exfiltration; no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV).
Server-side request forgery in Chaskiq through 2.0.3 allows unauthenticated attackers to make the server fetch arbitrary URLs-including internal network resources and cloud instance metadata endpoints-by submitting crafted requests to the createUrlUpload GraphQL mutation. The fetched content is stored as an ActiveStorage blob and returned to the attacker, enabling exfiltration of sensitive data such as IAM credentials from IMDSv1 endpoints. With a CVSS 9.2 severity and no authentication required, this is a high-priority issue; at time of analysis, no public exploit code was identified, though a technical writeup is publicly available. Note: confirmed actively exploited (CISA KEV) is not applicable; no public exploit identified at time of analysis.
Server-side request forgery in Wegow's ticket sales chart PDF export allows an authenticated promoter to inject malicious SVG content into the export request, causing the third-party Highcharts cloud service to fetch attacker-controlled external resources and embed the responses in the generated PDF. This provides a request proxying/laundering capability constrained to what the external SaaS can reach, and no public exploit has been identified at time of analysis. The CVSS 4.0 base score is 7.1 (High), driven almost entirely by high integrity impact (VI:H) while confidentiality and availability impacts are none, an unusual weighting for an SSRF which more typically carries a confidentiality impact.
Server-side request forgery in JobOps through 0.13.1 lets a caller submit an arbitrary url value to the POST /api/manual-jobs/fetch handler and have the server fetch internal destinations, with the response body returned to the caller, exposing loopback services, private-range hosts, and cloud instance metadata such as the 169.254.169.254 endpoint. In a standard deployment the request must carry valid authentication (PR:L per the assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), but when the instance is running in demo mode unauthenticated clients can trigger the identical request, which is the configuration that removes the authentication barrier. Impact is confidentiality-only at 7.1 (no integrity or availability effect, no user interaction), and exploitation succeeds only if the target internal destination is network-reachable from the JobOps server; no public exploit code was identified at time of analysis, although a public technical writeup describing the flaw exists, and no KEV listing appears in the provided intelligence.
Server-side request forgery in PhastPress affects WordPress sites running the optional PhastPress performance plugin through version 3.10, allowing unauthenticated remote attackers to make the server fetch arbitrary URLs by spoofing the HTTP Host header. Because the plugin builds its scripts-service URL whitelist from that attacker-controlled header, no login, user interaction, or non-default configuration is required; impact is limited to the response data and any reachable internal or external services the WordPress host can access. No public exploit identified at time of analysis, and EPSS is not supplied in the source data, so this is a genuine but not top-priority SSRF risk pending patch adoption.
Server-side request forgery in Renovate before 44.79.0 allows authenticated users with low privileges to direct the shared HTTP client at arbitrary internal URLs through 'extends' preset references or 'customDatasources' entries. An attacker who can influence Renovate's configuration - for example by committing to a scanned repository or controlling a preset source - can reach an instance metadata endpoint such as AWS IMDS to obtain credentials, or exfiltrate sensitive information into Renovate logs; real-world impact depends on the deployment's network reachability of internal services. The vendor fixed the issue in Renovate 44.79.0, and no public exploit code has been identified at time of analysis.
TurboDocx html-to-docx through 1.23.1 is vulnerable to server-side request forgery (CWE-918): when an application converts attacker-supplied HTML to DOCX with remote image handling enabled, the library dereferences <img src> URLs server-side, and a loose isValidUrl() check allows loopback, RFC1918 private, and cloud metadata addresses (e.g. 169.254.169.254) to be requested and their responses embedded into the generated document's word/media folder. The flaw is remotely reachable without authentication or user interaction (CVSS:4.0 PR:N/UI:N, 8.2; independent assessment CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), and publicly available exploit code exists, though there is no confirmed active exploitation (no CISA KEV listing) and no vendor-released patch identified at time of analysis. Real-world risk is conditional rather than universal: the attacker must supply a live, responsive internal target, the fetched response must be readable from the returned DOCX, and deployments that disable remote image fetching, filter outbound traffic, or restrict HTML input are not exploitable.
Unauthenticated server-side request forgery in Kan 0.5.5 through 0.6.0 allows remote attackers to make the server issue arbitrary outbound HTTP requests through the /api/download/attatchment route by supplying a crafted url query parameter. The flaw is an incomplete fix for CVE-2026-32255 and only manifests when the S3_ENDPOINT environment variable is unset or blank - the configuration the project's own .env.example documents as the intended setup for AWS S3 - in which case hostname validation is skipped entirely and the attacker-controlled URL is handed directly to fetch(). No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing), but EPSS/scoring data and the unauthenticated network vector (CVSS 4.0 base 9.2, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) make this a high-priority fix for exposed deployments.
Server-side request forgery in Adobe Content Credentials (CAI Content Credentials SDK) allows unauthenticated remote attackers to induce the server to make arbitrary outbound requests, potentially reaching internal services and escalating privileges. The CVSS 3.1 base score is 8.6 (HIGH) with a changed scope, high confidentiality impact, and no integrity or availability impact. Exploitation requires no user interaction; no public exploit code has been identified at time of analysis, and the vendor advisory APSB26-163 should be consulted for fixes.
Server-side request forgery in Adobe ColdFusion 2023 (up to and including 2023.0.25) and ColdFusion 2025 (up to and including 2025.0.13) allows an authenticated low-privileged attacker to coerce the application server into issuing requests to internal resources, yielding elevated access and disclosure of data outside the attacker's intended scope. Adobe assigns this a CVSS 3.1 base score of 7.1 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N); exploitation is non-deterministic because the vendor states success depends on conditions beyond the attacker's control, and it requires an existing foothold as a low-privileged account. There is no public exploit identified at time of analysis and no CISA KEV listing, so the practical risk profile is that of a moderate-severity, post-authentication SSRF rather than a remotely exploitable unauthenticated flaw.
Authenticated blind server-side request forgery in Tandoor Recipes before 2.6.10 allows a user with privileges to create a Space and configure an AI provider URL to force the server to connect to arbitrary internal addresses. The AI actions behind TARGET/api/ai-import/ and api/ai-step-sort/ pass the attacker-supplied provider URL straight to LiteLLM, bypassing the application's safe_request outbound filtering, and the resulting connection success, refusal, or timeout is surfaced as a reachability oracle that can be used to map internal hosts, ports, and cloud metadata endpoints. Exploitation requires an authenticated account (PR:L) and the AI provider feature to be in use, and exposure is limited to a blind oracle rather than confirmed response-body exfiltration; no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV).
Server-side request forgery in Chaskiq through 2.0.3 allows unauthenticated attackers to make the server fetch arbitrary URLs-including internal network resources and cloud instance metadata endpoints-by submitting crafted requests to the createUrlUpload GraphQL mutation. The fetched content is stored as an ActiveStorage blob and returned to the attacker, enabling exfiltration of sensitive data such as IAM credentials from IMDSv1 endpoints. With a CVSS 9.2 severity and no authentication required, this is a high-priority issue; at time of analysis, no public exploit code was identified, though a technical writeup is publicly available. Note: confirmed actively exploited (CISA KEV) is not applicable; no public exploit identified at time of analysis.
Server-side request forgery in Wegow's ticket sales chart PDF export allows an authenticated promoter to inject malicious SVG content into the export request, causing the third-party Highcharts cloud service to fetch attacker-controlled external resources and embed the responses in the generated PDF. This provides a request proxying/laundering capability constrained to what the external SaaS can reach, and no public exploit has been identified at time of analysis. The CVSS 4.0 base score is 7.1 (High), driven almost entirely by high integrity impact (VI:H) while confidentiality and availability impacts are none, an unusual weighting for an SSRF which more typically carries a confidentiality impact.
Server-side request forgery in JobOps through 0.13.1 lets a caller submit an arbitrary url value to the POST /api/manual-jobs/fetch handler and have the server fetch internal destinations, with the response body returned to the caller, exposing loopback services, private-range hosts, and cloud instance metadata such as the 169.254.169.254 endpoint. In a standard deployment the request must carry valid authentication (PR:L per the assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), but when the instance is running in demo mode unauthenticated clients can trigger the identical request, which is the configuration that removes the authentication barrier. Impact is confidentiality-only at 7.1 (no integrity or availability effect, no user interaction), and exploitation succeeds only if the target internal destination is network-reachable from the JobOps server; no public exploit code was identified at time of analysis, although a public technical writeup describing the flaw exists, and no KEV listing appears in the provided intelligence.
Server-side request forgery in PhastPress affects WordPress sites running the optional PhastPress performance plugin through version 3.10, allowing unauthenticated remote attackers to make the server fetch arbitrary URLs by spoofing the HTTP Host header. Because the plugin builds its scripts-service URL whitelist from that attacker-controlled header, no login, user interaction, or non-default configuration is required; impact is limited to the response data and any reachable internal or external services the WordPress host can access. No public exploit identified at time of analysis, and EPSS is not supplied in the source data, so this is a genuine but not top-priority SSRF risk pending patch adoption.
Server-side request forgery in Renovate before 44.79.0 allows authenticated users with low privileges to direct the shared HTTP client at arbitrary internal URLs through 'extends' preset references or 'customDatasources' entries. An attacker who can influence Renovate's configuration - for example by committing to a scanned repository or controlling a preset source - can reach an instance metadata endpoint such as AWS IMDS to obtain credentials, or exfiltrate sensitive information into Renovate logs; real-world impact depends on the deployment's network reachability of internal services. The vendor fixed the issue in Renovate 44.79.0, and no public exploit code has been identified at time of analysis.
TurboDocx html-to-docx through 1.23.1 is vulnerable to server-side request forgery (CWE-918): when an application converts attacker-supplied HTML to DOCX with remote image handling enabled, the library dereferences <img src> URLs server-side, and a loose isValidUrl() check allows loopback, RFC1918 private, and cloud metadata addresses (e.g. 169.254.169.254) to be requested and their responses embedded into the generated document's word/media folder. The flaw is remotely reachable without authentication or user interaction (CVSS:4.0 PR:N/UI:N, 8.2; independent assessment CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), and publicly available exploit code exists, though there is no confirmed active exploitation (no CISA KEV listing) and no vendor-released patch identified at time of analysis. Real-world risk is conditional rather than universal: the attacker must supply a live, responsive internal target, the fetched response must be readable from the returned DOCX, and deployments that disable remote image fetching, filter outbound traffic, or restrict HTML input are not exploitable.
Unauthenticated server-side request forgery in Kan 0.5.5 through 0.6.0 allows remote attackers to make the server issue arbitrary outbound HTTP requests through the /api/download/attatchment route by supplying a crafted url query parameter. The flaw is an incomplete fix for CVE-2026-32255 and only manifests when the S3_ENDPOINT environment variable is unset or blank - the configuration the project's own .env.example documents as the intended setup for AWS S3 - in which case hostname validation is skipped entirely and the attacker-controlled URL is handed directly to fetch(). No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing), but EPSS/scoring data and the unauthenticated network vector (CVSS 4.0 base 9.2, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) make this a high-priority fix for exposed deployments.
Server-side request forgery in Adobe Content Credentials (CAI Content Credentials SDK) allows unauthenticated remote attackers to induce the server to make arbitrary outbound requests, potentially reaching internal services and escalating privileges. The CVSS 3.1 base score is 8.6 (HIGH) with a changed scope, high confidentiality impact, and no integrity or availability impact. Exploitation requires no user interaction; no public exploit code has been identified at time of analysis, and the vendor advisory APSB26-163 should be consulted for fixes.
Server-side request forgery in Adobe ColdFusion 2023 (up to and including 2023.0.25) and ColdFusion 2025 (up to and including 2025.0.13) allows an authenticated low-privileged attacker to coerce the application server into issuing requests to internal resources, yielding elevated access and disclosure of data outside the attacker's intended scope. Adobe assigns this a CVSS 3.1 base score of 7.1 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N); exploitation is non-deterministic because the vendor states success depends on conditions beyond the attacker's control, and it requires an existing foothold as a low-privileged account. There is no public exploit identified at time of analysis and no CISA KEV listing, so the practical risk profile is that of a moderate-severity, post-authentication SSRF rather than a remotely exploitable unauthenticated flaw.