Unauthorized workspace access via unchecked domain
Published Dec 14, 2025 · Updated Dec 14, 2025
Improper access control in deco CMS MCP Mesh 1.0.0-alpha.31 and earlier allows remote attackers to join arbitrary workspaces. The autoJoinTeam tool trusts its supplied domain when selecting a team without verifying that it matches the caller's email domain. Knowing a workspace domain and reaching the auto-join flow is sufficient to gain membership and its associated workspace access.
Summary
What happened
Improper access control in deco CMS MCP Mesh 1.0.0-alpha.31 and earlier allows remote attackers to join arbitrary workspaces. The autoJoinTeam tool trusts its supplied domain when selecting a team without verifying that it matches the caller's email domain. Knowing a workspace domain and reaching the auto-join flow is sufficient to gain membership and its associated workspace access.
The record
- CVE
- CVE-2025-14660
- Published
- Dec 14, 2025
- Updated
- Dec 14, 2025
- Vendor
- deco CMS
- Product
- MCP Mesh
- Classifications
- CWE-266, CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2025CVE publishedPublication date reported by the CVE source.
- Dec 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0-alpha.0
- Affected versionversion=1.0.0-alpha.1
- Affected versionversion=1.0.0-alpha.10
- Affected versionversion=1.0.0-alpha.11
- Affected versionversion=1.0.0-alpha.12
- Affected versionversion=1.0.0-alpha.13
- Affected versionversion=1.0.0-alpha.14
- Affected versionversion=1.0.0-alpha.15
- Affected versionversion=1.0.0-alpha.16
- Affected versionversion=1.0.0-alpha.17
- Affected versionversion=1.0.0-alpha.18
- Affected versionversion=1.0.0-alpha.19
- Affected versionversion=1.0.0-alpha.2
- Affected versionversion=1.0.0-alpha.20
- Affected versionversion=1.0.0-alpha.21
- Affected versionversion=1.0.0-alpha.22
- Affected versionversion=1.0.0-alpha.23
- Affected versionversion=1.0.0-alpha.24
- Affected versionversion=1.0.0-alpha.25
- Affected versionversion=1.0.0-alpha.26
- Affected versionversion=1.0.0-alpha.27
- Affected versionversion=1.0.0-alpha.28
- Affected versionversion=1.0.0-alpha.29
- Affected versionversion=1.0.0-alpha.3
- Affected versionversion=1.0.0-alpha.30
- Affected versionversion=1.0.0-alpha.31
- Affected versionversion=1.0.0-alpha.4
- Affected versionversion=1.0.0-alpha.5
- Affected versionversion=1.0.0-alpha.6
- Affected versionversion=1.0.0-alpha.7
- Affected versionversion=1.0.0-alpha.8
- Affected versionversion=1.0.0-alpha.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Workspace auto-join proof-of-concept videoproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo