Postiz App has a High-Severity SSRF Vulnerability via Next.js

published 2026-03-27 7mo ago modified 2026-03-27 7mo ago

cvss: 7.5; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### Impact A successful SSRF attack allows an attacker to: - Bypass firewalls to scan and interact with internal network services/ports. - Access sensitive cloud metadata services (e.g., AWS IMDS 169.254.169.254) to potentially leak instance credentials. - Pivot into the internal network environment where Postiz is hosted.

### Workarounds There are no workarounds known to this, please upgrade to Postiz version `v2.21.1`.

Is GHSA-vj2p-7pgw-g2wf in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	postiz	<=2.0.12	no fix listed

Classification

Weakness

CWE-1395 Dependency on Vulnerable Third-Party Component
CWE-918 Server-Side Request Forgery

References

Sources

GitHub Advisory GHSA-vj2p-7pgw-g2wf

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.