Skip to main content

Postiz CVE-2026-48783

| EUVDEUVD-2026-37507 MEDIUM
Insufficient Verification of Data Authenticity (CWE-345)
2026-06-16 GitHub_M
4.8
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain or intercept NowPayments-signed callback token
  2. Delivery
    POST token to unauthenticated /public/modify-subscription
  3. Exploit
    Assert free-tier plan in token claims
  4. Execution
    Server executes enforcement side effects without purpose validation
  5. Impact
    Own organization integrations disabled and post crons reset

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Data authenticity verification
Exploitation Conditions

Exploitation requires two specific conditions: first, a validly signed token accepted by the /public/modify-subscription endpoint, originating from the NowPayments crypto payment integration signing key - either intercepted from a prior payment callback or derived from knowledge of the key; second, the target Postiz instance must have had the NowPayments crypto payment feature configured and active (non-default for most deployments without a configured NowPayments API key). Impact is categorically limited to the attacker's own organization - the endpoint does not accept organization IDs from the caller that differ from those encoded in the token's claims, preventing cross-tenant attacks. The AC:H CVSS metric quantifies the key barrier: obtaining or forging a valid signed token is the primary obstacle to exploitation. No Postiz account authentication is required by the endpoint itself.

Impact

The CVSS 3.1 score of 4.8 (Medium) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L is consistent with the described constraints. The AC:H metric is the critical signal: exploitation requires obtaining or crafting a token that the endpoint accepts, implying access to the NowPayments signing key or a replayable prior payment callback token - a non-trivial barrier. The PR:N metric reflects that no Postiz authentication is required by the endpoint itself, but the token requirement acts as an indirect credential. No EPSS score was provided in the source data, and neither a CISA KEV listing nor public POC code has been identified, further reducing urgency. The strongest real-world mitigant is the strict self-tenancy limitation: the endpoint cannot be used to sabotage other organizations' integrations or schedules. The integrity and availability impacts (I:L, A:L) are real but operationally bounded - disabling integrations and resetting crons within one's own organization is disruptive but not catastrophic. This is a genuine Medium and not a high-CVSS-but-low-risk mismatch; the score accurately reflects the constrained impact and elevated attack complexity.

Exploit ScenarioDerived

An attacker who has previously completed or intercepted a NowPayments crypto payment flow for their own Postiz organization captures a validly signed callback token from that flow. They replay this token in a POST request to /public/modify-subscription with claims asserting a free-tier plan, causing their organization's social media integrations above the free-plan limit to be disabled and the scheduled-post cron to be reset - effectively disrupting their own Postiz service. No public exploit code has been identified at time of analysis, and crafting a fresh token without access to the signing key is not feasible.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 17, 2026

Unauthenticated exploitation of Postiz's /public/modify-subscription endpoint allowed any caller in possession of a validly signed NowPayments callback token to trigger subscription enforcement side effects against their own organization - disabling team members, dropping integrations, and resetting the scheduled-post cron - without Postiz authentication. The flaw (CWE-345) stems from the NowPayments crypto payment integration: the endpoint verified the token's cryptographic signature but never validated its intended purpose or bound it to a specific subscription-modification context. Impact is strictly self-contained; the endpoint cannot be redirected at other tenants. No public exploit code and no CISA KEV listing have been identified at time of analysis. The issue is fixed in Postiz 2.21.8.

RemediationAI

Upgrade Postiz to version 2.21.8, confirmed as the vendor-released patch via the GitHub release at https://github.com/gitroomhq/postiz-app/releases/tag/v2.21.8 and commit 23696d2973510ae1f3f48bfa41a6bfbbf9827b05. The fix eliminates the vulnerable endpoint entirely by removing the NowPayments crypto payment module. If an immediate upgrade is not feasible, operators should block external HTTP access to the /public/modify-subscription path at the reverse proxy or WAF layer; be aware this will also deny access to other unauthenticated public routes (e.g., OAuth callbacks) hosted under the same /public/ prefix, so test for side effects before applying. Restricting inbound traffic to known NowPayments IP ranges at the network boundary is an additional compensating control, though IP allowlists can be bypassed if the signing key is compromised. The vendor advisory at https://gadvisory.org/advisories/PSA-2026-WWFR8X provides supplemental remediation guidance.

Affected VersionsENISA

postiz-app < 2.21.8

Affected Packages

euvd postiz_app fix: 2.21.8

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Postiz (cpe:2.3:a:gitroomhq:postiz-app) is a NestJS-based AI social media scheduling platform. The vulnerable component was the /public/modify-subscription endpoint wired into the NowPayments crypto billing integration, which accepted a signed token and executed subscription enforcement logic (team-member state, integration count limits, cron scheduling) based on the plan tier asserted in the token's claims. The root cause is CWE-345 (Insufficient Verification of Data Authenticity): a confused-deputy pattern in which the server verified the token's cryptographic signature but omitted any check of the token's audience, scope, or purpose binding. Any signed token from the NowPayments flow - regardless of the action it was originally issued for - could be replayed against the subscription endpoint. The fix at commit 23696d2973510ae1f3f48bfa41a6bfbbf9827b05 removed the entire Nowpayments module and its public endpoints from the NestJS module, controller, and billing controller. The same patch also hardened the auth middleware to re-resolve users from the database rather than trusting JWT body claims directly, and stripped credential fields (token, refreshToken, customInstanceDetails) from integration API responses.

Know when Postiz App gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 4.8 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
vuln.today AI 4.8 MEDIUM

Network-accessible but requires a valid external signed token (AC:H); no Postiz auth needed (PR:N); no confidentiality impact; self-contained integrity and availability degradation only.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

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

Lifecycle Timeline

1
Patch available
Jun 16, 2026 - 23:02 EUVD

DescriptionCVE.org

Postiz is an AI social media scheduling tool. Versions prior to 2.21.8 contained an unauthenticated endpoint that accepted a signed token and applied subscription-enforcement side effects to the organization referenced in that token's claims, without verifying the token's intended purpose. The endpoint, /public/modify-subscription, could not change the persisted subscription tier, but it did execute enforcement-related side effects on the caller's own organization, including adjusting team-member enablement state, disabling integrations exceeding the asserted plan's limits, and resetting the scheduled-post cron when the asserted plan was the free tier. Impact is limited to the attacker's own organization and cannot be redirected at other tenants through this endpoint. This issue has been fixed in version 2.21.8.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

24
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-40487 CRITICAL POC
9.0 Apr 18

File upload validation bypass in Postiz social media scheduler (versions before 2.21.6) allows authenticated users to up

CVE-2026-115931 CRITICAL
9.9 Oct 23

Postiz (gitroomhq/postiz-app) before v2.25.1 allows any signed-in user to invoke arbitrary internal integration methods

CVE-2026-48781 CRITICAL
9.9 Jun 16

Privilege escalation to SUPERADMIN in Postiz (gitroomhq/postiz-app) versions prior to 2.21.8 allows any authenticated us

CVE-2026-115933 CRITICAL
9.9 Oct 24

Improper token-purpose validation in Postiz (gitroomhq/postiz-app) through v2.25.2 allows any authenticated user holding

CVE-2026-42298 CRITICAL
9.8 May 08

Arbitrary code execution and privileged token theft affects Postiz (gitroomhq/postiz-app) prior to commit da44801 throug

CVE-2026-115932 CRITICAL
9.6 Oct 24

Postiz instances older than v2.25.3 that store media on local disk let a registered user have the publishing worker read

CVE-2026-19264 CRITICAL
9.3 Aug 07

Arbitrary file read in Postiz (gitroomhq/postiz-app before 2.22.1) lets an unauthenticated remote attacker retrieve any

CVE-2026-94456 CRITICAL
9.1 Sep 22

Predictable, non-cryptographic credential generation in Postiz (gitroomhq/postiz-app, all versions prior to v2.24.0) all

CVE-2026-42556 CRITICAL
9.0 May 08

Stored cross-site scripting in Postiz (gitroomhq/postiz-app) versions 2.21.6 through 2.21.6 lets any authenticated user

CVE-2026-34577 HIGH
8.6 Apr 02

Server-side request forgery in Postiz AI social media scheduling tool (versions < 2.21.3) allows unauthenticated remote

CVE-2026-34576 HIGH
8.3 Apr 02

Server-side request forgery (SSRF) in Postiz social media scheduling tool versions prior to 2.21.3 allows authenticated

CVE-2026-40168 HIGH
8.2 Apr 10

Server-side request forgery in Postiz (gitroomhq postiz-app) versions prior to 2.21.5 allows unauthenticated remote atta

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy