Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged tenant user
-
ExploitEnumerate sequential assistant appIds
-
ExecutionSend DELETE /v1/appspace/app with victim appId
-
ImpactPermanently delete victim apps, workflows and data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires a valid authenticated low-privileged account on a Wanwu instance running a version before 0.6.3 (PR:L), and a multi-tenant deployment where other tenants' agent or RAG applications exist to be targeted. The core prerequisite is that the pre-patch DELETE /v1/appspace/app handler performs no ownership check tying the supplied appId to the caller's user/org; exploitation is further eased because assistant appIds are sequential and therefore guessable, enabling enumeration. Limiting factors: the attacker must be authenticated (no anonymous/unauthenticated path), no user interaction is required, and the impact is scoped to applications reachable within the same Wanwu instance. |
| Impact | Signals are largely consistent and point to a genuine but bounded integrity/availability risk rather than a critical mass-exploitation threat. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H) correctly frames this as a network-reachable, low-complexity attack requiring an authenticated low-privileged account (PR:L), with no confidentiality impact but high integrity and availability impact - matching the description of permanent cross-tenant deletion of applications and data. There is no confidentiality loss because the IDOR enables destruction, not disclosure. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so exploitation status is 'no public exploit identified at time of analysis' despite a detailed technical writeup on HackMD describing the flaw. The SSVC-style picture is: exploitation not observed, automatable=yes (sequential/guessable appIds make enumeration trivial per the description), technical impact=partial-to-total for the victim tenant's data. This is a real priority for anyone running a multi-tenant Wanwu deployment with untrusted tenants, but the PR:L requirement and the niche product footprint cap widespread opportunistic exploitation. The vendor-confirmed patch (ownership/UserId+OrgId checks added) makes remediation straightforward. No conflicting signals were detected; the main gap is the absence of EPSS/KEV/POC data, which is a data-availability limitation, not evidence of low risk. |
| Exploit ScenarioDerived | An attacker registers or already holds a low-privileged account on a shared multi-tenant Wanwu instance, then scripts requests to DELETE /v1/appspace/app iterating over sequential assistant/appId values belonging to other tenants. Because the pre-0.6.3 handler does not verify that the caller owns the target appId, each request permanently destroys a victim tenant's agent or RAG application along with its workflows, conversations, and associated data. A detailed technical writeup exists (HackMD) but no weaponized public exploit code was provided. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Authenticated low-privileged users on UnicomAI Wanwu deployments running versions before 0.6.3 can permanently delete other tenants' agent and RAG applications by sending a DELETE request to /v1/appspace/app with a guessed appId, because the pre-patch handler performs no ownership check on the supplied identifier. The vulnerability is an IDOR (CWE-639) and is exacerbated by sequential, predictable assistant IDs, which makes enumeration of victims' appIds practical; deletion also cascades to associated workflows, conversations, and linked data, giving high integrity and availability impact (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, vendor score 7.2). Exploitation requires a valid low-privileged account on a multi-tenant instance with other tenants' applications present, and no public exploit code has been identified at time of analysis, though a detailed technical writeup and patch commit are publicly available.
RemediationAI
Upgrade to UnicomAI Wanwu 0.6.3, which contains the vendor fix, or apply the upstream patch commit 13d0b225ec237d5a0b44730b2331efadaeb462a2 (available at https://github.com/UnicomAI/wanwu/commit/13d0b225ec237d5a0b44730b2331efadaeb462a2, with the release at https://github.com/UnicomAI/wanwu/releases/tag/v0.6.3); this is the only remediation that closes the object-level authorization gap. If immediate upgrade is not possible, compensating controls should reduce exposure while accepting residual risk: restrict network access to the /v1/appspace/app endpoint and the BFF/admin API to trusted networks or a VPN (trade-off: blocks legitimate remote users but prevents external ID enumeration), and where practical operate Wanwu in single-tenant or per-team isolated instances so an authenticated low-privileged user has no other tenants' applications in scope (trade-off: higher infrastructure overhead and loss of shared-resource convenience). Because assistant IDs are sequential and guessable, defenders should treat any DELETE /v1/appspace/app calls that target appIds outside the caller's own user/org scope as suspicious and alert on them, and should restrict who can obtain low-privileged accounts on shared instances. Backups or soft-delete retention for applications, workflows, and conversations provide recovery capability if deletion occurs, but they do not prevent the unauthorized destructive action itself.
Affected VersionsENISA
Affected Packages
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
UnicomAI Wanwu is a Go-based open-source AI agent/RAG platform whose backend-for-frontend (BFF) service exposes application-space operations over a protobuf/gRPC-backed API. The flaw is an insecure direct object reference (CWE-639) in the appspace service: the pre-fix DeleteApp and related delete handlers (see internal/bff-service/service/appspace.go#L20-L58 in v0.6.2) accepted only an object identifier (appId) plus app type, with no user or organization scoping bound to the request, so authorization was effectively delegated to the client-supplied ID. The upstream fix commit 13d0b225ec237d5a0b44730b2331efadaeb462a2 hardens this by adding UserId and OrgId fields to the DeleteAppReq, DelAppKeyReq, DeleteApiKeyReq, and AppUrlDeleteReq protobuf messages (and their generated Go structs and getters), forcing server-side ownership validation against the caller's identity. The affected CPE cpe:2.3:a:unicomai:wanwu:*:*:*:*:*:*:*:* marks all versions prior to the fixed release as vulnerable. Attackers exploit the missing object-level authorization by iterating sequential numeric assistant IDs against DELETE /v1/appspace/app, deleting any matching application regardless of tenant.
Know when Wanwu 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Network-reachable REST endpoint (AV:N/AC:L), requires any low-privileged authenticated account (PR:L), no UI; permanent cross-tenant deletion gives high integrity and availability impact but no data disclosure (C:N).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
UnicomAI Wanwu before 0.6.3 contains an insecure direct object reference vulnerability that allows authenticated low-privileged users to delete other tenants' agent or RAG applications by supplying their appId. Attackers can send requests to DELETE /v1/appspace/app with guessed sequential assistant IDs to permanently delete victims' applications, workflows, conversations, and associated data.
Executive ViewAI
UnicomAI Wanwu deployments running versions prior to 0.6.3 expose multi-tenant customers to cross-tenant application deletion by any authenticated low-privileged user, potentially destroying agent and RAG applications along with linked workflows and conversation data. This tenant-isolation failure can cause permanent data loss, operational disruption, and reputational harm across customers sharing the platform, making remediation a priority for security and product leadership.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Authenticated, enabled users of UnicomAI Wanwu (also tracked as unicomai/wanwu) before version 0.6.3 can revoke other or
Missing authorization in UnicomAI Wanwu through 0.6.5 lets any authenticated, enabled user revoke other users' AppKeys b
Authorization bypass in UnicomAI Wanwu through 0.6.5 allows any authenticated user to mint an AppKey bound to another us
EUVD-2026-97004
GHSA-fg7x-9rxv-3m3p
NVD
CVE.org
EPSS
Exploit-DB