GHSA-89V5-38XR-9M4J

Postiz has Multiple SSRF Vectors - Webhooks, RSS Feed, URL Loader

async sendWebhook(@Body() body: any, @Query('url') url: string) {
  try {
    await fetch(url, {  // No URL validation
      method: 'POST',
      body: JSON.stringify(body),
      headers: { 'Content-Type': 'application/json' },
    });
  } catch (err) { }
  return { send: true };
}

async sendWebhooks(postId: string, orgId: string, integrationId: string) {
  const webhooks = await this._webhookService.getWebhooks(orgId);
  return Promise.all(
    webhooks.map(async (webhook) => {
      await fetch(webhook.url, {  // Stored URL, no validation
        method: 'POST',
        body: JSON.stringify(post),
      });
    })
  );
}

async loadXML(url: string) {
  const { items } = await parser.parseURL(url);  // No URL validation
}

async loadUrl(url: string) {
  const loadDom = new JSDOM(await (await fetch(url)).text());  // No validation
}

• Cloud metadata theft: AWS/GCP/Azure credentials
• Internal network scanning: Full access to private IP ranges
• Multiple entry points: Webhooks, RSS feeds, URL loader all vulnerable

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-89V5-38XR-9M4J? GHSA-89V5-38XR-9M4J is a high-severity server-side request forgery (SSRF) vulnerability in postiz (npm), affecting versions <= 2.0.12. No fixed version is listed yet. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. Which versions of postiz are affected by GHSA-89V5-38XR-9M4J? postiz (npm) versions <= 2.0.12 is affected.
3. Is there a fix for GHSA-89V5-38XR-9M4J? No fixed version is listed for GHSA-89V5-38XR-9M4J yet. Monitor the advisory for updates and apply mitigations in the interim.
4. Is GHSA-89V5-38XR-9M4J exploitable, and should I be worried? Whether GHSA-89V5-38XR-9M4J is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether GHSA-89V5-38XR-9M4J is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix GHSA-89V5-38XR-9M4J? No fixed version is listed yet. In the interim: Validate and restrict destination URLs against an allowlist. Block requests to private IP ranges and cloud metadata endpoints.

Other vulnerabilities in postiz