Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-63647 – Unauthenticated SSE Notification Stream Hijack (Auth Bypass) – CordysCRM < 1.7.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-63647 is a critical missing-authentication vulnerability (CWE-306, CWE-639) in 1Panel-dev’s CordysCRM, an open-source CRM platform. The SSE (Server-Sent Events) endpoints used for real-time notifications are exposed without any authentication check, allowing unauthenticated network attackers to hijack, inject into, or terminate other users’ notification streams. The flaw is rated 9.3 (Critical) and affects all CordysCRM versions prior to 1.7.2.

Technical details

  • Root cause: CordysCRM’s SseController exposes the /sse/subscribe, /sse/broadcast, and /sse/close endpoints as anonymous/public paths in the application’s Shiro filter chain configuration (ShiroFilter.addPublicPathFilters).
  • These endpoints trust a caller-supplied userId parameter to identify the target notification stream instead of deriving identity from an authenticated session/principal.
  • Attack vector: network, no authentication or user interaction required — an attacker only needs to reach the exposed HTTP endpoints and supply an arbitrary userId.
  • Impact: an unauthenticated attacker can use /sse/subscribe to read another user’s workflow events, approval requests, mentions, and alerts; use /sse/broadcast to inject fabricated messages (e.g., fake heartbeat/system messages) into another user’s stream; and use /sse/close to forcibly terminate another user’s active notification channel, resulting in confidentiality, integrity, and availability impact.

Affected software

  • 1Panel-dev CordysCRM: all versions prior to 1.7.2

Severity

  • CVSS Base Score: 9.3 (Critical)
  • CVSS v4.0 Vector: AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade CordysCRM to version 1.7.2 or later, where the SSE endpoints have been secured behind proper authentication checks.
  • If immediate patching is not possible: restrict or block direct external access to the /sse/subscribe, /sse/broadcast, and /sse/close paths using a web application firewall or reverse proxy access controls, and review the Shiro filter chain configuration to ensure sensitive endpoints are not marked as public/anonymous.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge