CVE-2025-53641VulnerabilityPublished 11 Jul 2025

CVE-2025-53641: gitroomhq postiz-app · Server-Side Request Forgery (SSRF)

Affects gitroomhq postiz-appSource CVE Database V5

Not known to be exploited · CVSS 8.2 High : upgrade to 1.62.3 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.62.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitroomhq/postiz-app to 1.62.3.

Affected software

Product	Affected	Fixed in
GitHubgitroomhq/postiz-app`pkg:github/gitroomhq/postiz-app`Other threats	Affected <1.62.3 >=1.45.1	Fixed in 1.62.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify their Postiz application version and upgrade to version 1.62.3 or later, where the vulnerability is patched. If immediate upgrading is not feasible, implement strict network egress filtering on servers hosting Postiz to restrict outbound HTTP requests only to trusted destinations, thereby limiting SSRF exploitation scope. Employ Web Application Firewalls (WAFs) with custom rules to detect and block unusual HTTP header injections or suspicious outbound request patterns. Conduct thorough internal network segmentation to minimize the impact of potential SSRF exploitation, ensuring that critical internal services are not directly accessible from the Postiz server. Monitor application logs and network traffic for anomalous outbound requests originating from the Postiz server. Additionally, perform regular security assessments and penetration testing focusing on SSRF vectors to detect similar vulnerabilities. Educate development teams on secure coding practices to prevent header injection flaws in future releases. Finally, maintain an incident response plan tailored to SSRF incidents to enable rapid containment and remediation if exploitation is detected.

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.

Impact

For European organizations using the Postiz application versions between 1.45.1 and 1.62.3, this SSRF vulnerability poses a substantial risk. Exploitation could allow attackers to bypass perimeter defenses and access internal network resources, including sensitive databases, internal APIs, or cloud metadata services, potentially leading to data breaches or lateral movement within the network. Given Postiz's role in managing social media scheduling, compromise could also lead to unauthorized manipulation or leakage of scheduled content, damaging brand reputation. Additionally, attackers could use the SSRF to scan internal networks or pivot to other critical infrastructure, increasing the attack surface. The lack of required authentication means that attackers can exploit this vulnerability remotely without valid credentials, increasing the likelihood of attacks. European organizations with strict data protection regulations, such as GDPR, face increased compliance risks if sensitive data is exposed due to this vulnerability. The potential for internal reconnaissance and data exfiltration makes this a critical concern for enterprises, government agencies, and media companies relying on Postiz for social media management.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 18:01 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats