# CVE-2025-53641: Postiz allows header mutation in middleware facilitates resulting in SSRF

> Attackers can inject headers to trigger SSRF, allowing unauthorized outbound requests from the server.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 11 Jul 2025
- **Also known as:** GHSA-48c8-25jq-m55f

## What is CVE-2025-53641?

CVE-2025-53641 is a high-severity server-side request forgery vulnerability in gitroomhq postiz-app, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Postiz is an AI social media scheduling tool. From 1.45.1 to 1.62.3, the Postiz frontend application allows an attacker to inject arbitrary HTTP headers into the middleware pipeline. This flaw enables a server-side request forgery (SSRF) condition, which can be exploited to initiate unauthorized outbound requests from the server hosting the Postiz application. This vulnerability is fixed in 1.62.3.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-53641?


## How do I fix CVE-2025-53641?

No fix has been published for CVE-2025-53641 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53641 being exploited?

There is no known exploitation of CVE-2025-53641 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53641 and fix it if it is affected.

What it is: CVE-2025-53641 is a high-severity server-side request forgery vulnerability in gitroomhq postiz-app, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53641 in the wild and no public exploit code.

Affected product: gitroomhq postiz-app. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53641/ (Markdown: https://insights.sbomify.com/CVE-2025-53641/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53641
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53641
- OSV: https://osv.dev/vulnerability/CVE-2025-53641

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53641/
Summaries are generated and may contain mistakes; the official description above is the record.