Security readout for executives and security teams
Plain-English summary
A regular Zulip organization member could start a Stripe card update flow and, after completion, change the organization’s default payment method without billing privileges. This affected Zulip Cloud payment processing and has been patched in the referenced commit. Self-hosted deployments are stated as no longer affected and requiring no patch or upgrade.
Executive priority
Treat as high priority for Zulip Cloud customers because it affects payment control integrity. The issue is patched and not reported as actively exploited, so focus on confirming exposure, reviewing recent billing changes, and ensuring finance teams recognize any payment method updates.
Technical view
CVE-2026-25741 is a CWE-863 authorization flaw in Zulip. Before commit bf28c82dc9b1f630fa8e9106358771b20a0040f7, an API endpoint for creating a card update session during upgrade flow allowed organization-member privileges. Stripe webhook completion then updated the organization default payment method. CVSS 3.1 is 7.1, with low attack complexity and required low privileges.
Likely exposure
Primary exposure is Zulip Cloud organizations using the affected payment processing flow before the patch. The source states self-hosted deployments are no longer affected and require no patch or upgrade. No broader product exposure is identified in the provided sources.
Exploitation context
The provided sources do not report active exploitation, and this CVE is not marked in KEV. Abuse would require an authenticated organization member and completion of the Stripe card update flow. Impact is mainly unauthorized payment method integrity change, with limited availability concern reflected in CVSS.
Researcher notes
The key authorization gap is missing billing-specific permission enforcement on card update session creation. The downstream Stripe webhook applied the default payment method change after Checkout completion. Public evidence names the fixing commit but does not provide active exploitation evidence or additional affected deployment types.
Mitigation direction
- For Zulip Cloud, rely on the vendor-patched service and monitor vendor advisory updates.
- No self-hosted patch or upgrade is required per the advisory.
- Review billing role assignments and remove unnecessary organization membership access.
- Review recent payment method changes for unexpected updates.
Validation and detection
- Identify whether your organization uses Zulip Cloud or self-hosted Zulip.
- Check whether any unexpected default payment method changes occurred before the patch date.
- Confirm billing administrators recognize recent Stripe card update activity.
- Track the GitHub advisory and commit for any follow-up guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-25741 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L2.84.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/zulip/zulip/security/advisories/GHSA-vhhx-84f7-rc8jCVE reference · x_refsource_CONFIRM
- https://github.com/zulip/zulip/commit/bf28c82dc9b1f630fa8e9106358771b20a0040f7CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.