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

Back
New CVE Detected

CVE-2026-85667 – Unauthenticated Webhook Message Injection & SSRF – xiaobei ≤ 5.5.2

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-85667 is a critical missing-authentication vulnerability (CWE-306) affecting xiaobei, an open-source AI marketing/customer-acquisition agent developed by TeamWiseFlow. Versions through 5.5.2 fail to enforce authentication or signature validation on the product’s webhook endpoint, allowing any unauthenticated, network-based attacker to inject arbitrary messages into the agent’s processing pipeline. The flaw is rated CRITICAL with a CVSS v4.0 base score of 9.3.

Technical details

  • Root cause: The /webhook_worktool handler, implemented in awada/awada-server/src/routes/webhook-worktool.ts, accepts inbound webhook requests without verifying a signature, token, or any other form of authentication.
  • Trigger conditions: An attacker simply needs network access to the exposed webhook endpoint; no credentials, prior access, or user interaction are required.
  • Attack vector: Network (remote, unauthenticated HTTP requests to the webhook route).
  • Secondary issue: Once a malicious message is injected, the agent pipeline fetches media referenced by attacker-controlled URLs without validation, enabling Server-Side Request Forgery (SSRF) against internal services reachable from the xiaobei server.
  • Impact: Attackers can inject arbitrary content/commands into the agent’s message pipeline and pivot to internal network resources via SSRF, threatening the confidentiality and integrity of the affected system and any internal services it can reach.

Affected software

  • Vendor: TeamWiseFlow
  • Product: xiaobei
  • Versions affected: All versions through and including 5.5.2

Severity

  • CVSS v4.0: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 9.1 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade xiaobei to a release newer than 5.5.2 that implements authentication/signature validation on webhook endpoints. Confirm the specific fixed version with the vendor’s official release notes, as this was not explicitly published at disclosure time.
  • If no patch is available/applied:
    • Restrict network access to the /webhook_worktool endpoint (e.g., firewall rules, allow-listing known webhook source IPs) so it is not reachable from untrusted networks.
    • Place the webhook endpoint behind a reverse proxy or gateway that enforces authentication (e.g., HMAC signature verification, shared secret headers) before requests reach the application.
    • Disable or block outbound media-URL fetching from the agent pipeline, or route it through an egress proxy that blocks requests to internal/private IP ranges to mitigate the SSRF vector.
    • Monitor logs for unexpected inbound requests to the webhook path and unusual outbound requests originating from the xiaobei server.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge