Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
chatwoot-hook-inbox-idor — Chatwoot v4.19.1 - Medium: 6.6 - Remote admin - cross-tenant config - integration hook accepts a foreign inbox_id and forces pending status | Kitploit
Tools/GitHubGitHub/abraxas/chatwoot-hook-inbox-idor
Authentication & AuthorizationVulnerability AnalysisWeb Application ExploitationWeb SecurityPenetration TestingAPI SecurityLabs & Practice
GitHub
Share
abraxas/chatwoot-hook-inbox-idor

chatwoot-hook-inbox-idor

Chatwoot v4.19.1 - Medium: 6.6 - Remote admin - cross-tenant config - integration hook accepts a foreign inbox_id and forces pending status

View Repository
5 days agoNot yet reviewed

Abraxas Labs - chatwoot-hook-inbox-idor

chatwoot-hook-inbox-idor

A Chatwoot administrator can create an integration hook on another tenant's inbox by putting that inbox id in the request. The hook lands in the attacker's account, the victim's new conversations start pending, the create response echoes the victim's inbox name, and the victim cannot see or delete the hook that is changing their queue.

Class: Cross-tenant object reference / authorization bypass Reach: Remote, authenticated account administrator

Chatwoot v4.19.1 - caab07a8

IDno CVE yet
ClassCross-tenant object reference
ReachRemote (administrator of any account)
CWECWE-639 / CWE-863
CVSSMedium: 6.6 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
ProductChatwoot
Affectedv4.19.1 caab07a8f00032d5205b5a5d7e2eb0ba2f3d2d82
Authadministrator of any account on the instance
LicenseGNU Affero GPL v3.0
Labloopback Docker compose; Postgres, Redis, Puma, Sidekiq

What an attacker can do

PrivilegeMethod / sinkRecon / integrity / availabilityLab-proven or inferred
Attach a hook to a foreign inboxPOST /api/v1/accounts/:attacker/integrations/hooks with hook.inbox_id = victim inboxIntegrity (cross-tenant config)Lab-proven
Read the victim inbox name and idthe same response, hook.inboxRecon (tenant inventory)Lab-proven. inbox_name='Victim Support'
Force every new victim conversation to start pendingInboxBotStatus#dialogflow_active? reads inbox.hooksAvailability (workflow)Lab-proven. Status returns to open when the attacker deletes the hook
Hide the change from the victimthe hook belongs to the attacker's accountIntegrityLab-proven. Victim sees 0 dialogflow hooks, attacker sees 1
Keep it in place indefinitelythe victim has no id to deleteAvailabilityInferred from the same ownership split
Enumerate other tenants' inbox idsid probing against the create endpointReconInferred; the response carries inbox with a name only when the id exists
Read victim message content through the attacker's Dialogflow projectHookListener#execute_hooksn/aClosed: the listener walks message.account.hooks, so the foreign hook never receives the victim's messages

Stays closed on this leftover

AxisMethod / sinkWhy it is closed
ReconDirect inbox readInboxPolicy#show? is account-scoped; lab returns 401
ReconMessage content to the attacker's botHookListener filters on the message's own account
IntegrityMoving or deleting the victim's own hooksHook ids are resolved through Current.account.hooks
IntegrityCreating a hook in the victim's accountCurrent.account.hooks.create! scopes the owner; only inbox_id escapes

How I found it

The hooks controller permits a field it never scopes:

def create
  @hook = Current.account.hooks.create!(permitted_params)
end

def permitted_params
  params.require(:hook).permit(:app_id, :inbox_id, :status, settings: {})
end

Current.account owns the row, so the hook cannot be read or deleted by the victim. inbox_id is taken as given. The model has no matching validation: belongs_to :inbox, optional: true and validates :inbox_id, presence: true, if: -> { hook_type == 'inbox' }. Nothing compares the inbox's account to the hook's.

Inbox#has_many :hooks, class_name: 'Integrations::Hook' is an ordinary inbox_id association, so the victim's inbox now reports an active bot:

def dialogflow_active?
  hooks.exists?(app_id: %w[dialogflow], status: 'enabled')
end

and Conversation#determine_conversation_status turns that into status = :pending for every new conversation. The create response renders _hook.json.jbuilder, which includes json.inbox resource.inbox&.slice(:id, :name), so the attacker also learns the victim inbox name.

Wrong turns: I expected the Dialogflow hook to also ship the victim's messages to the attacker's GCP project, which would have made this a data-exfiltration bug. The listener walks message.account.hooks, and the hook is in the attacker's account, so it never fires for the victim's messages. The lab keeps that as a closed axis instead of an overclaim.

Lab

python3 chatwoot-hook-inbox-idor-Abraxas-Labs.py

or:

cd lab
./run.sh

Two tenants, an inbox each, one contact in the victim tenant. The PoC creates a control conversation that must be open, creates the hook with the victim's inbox_id, checks the echoed name, proves the attacker still cannot read the victim inbox over HTTP, creates a second victim conversation that must now be pending, compares both tenants' integration views, then deletes the hook and confirms the victim's queue recovers.

IOC control_conversation status='open' inbox=1
IOC hook_created id=1 account_id=1 inbox_id=1 inbox_name='Victim Support' status=True
IOC control_victim_reads_own_inbox status=200
IOC control_attacker_reads_victim_inbox status=401
IOC victim_conversation_after_hook status='pending'
IOC victim_visible_dialogflow_hooks=0 attacker_visible_dialogflow_hooks=1
IOC after_attacker_cleanup status='open'
SUCCESS CHATWOOT-F4-HOOK-INBOX-IDOR attacker_account=1 victim_account=2 victim_inbox=1 hook=1 victim_conversation_status=pending victim_cannot_see_hook=true inbox_name='Victim Support' VICTIM-INBOX-NAME-LEAK

run.sh tears the stack down on exit.

The fix

Validate the inbox against the account in Integrations::Hook, for example validate :inbox_belongs_to_account, comparing inbox.account_id with account_id when both are present. Do it on the model so every write path inherits it, and keep the controller permit list as is.

References

  • chatwoot/chatwoot caab07a8f00032d5205b5a5d7e2eb0ba2f3d2d82
  • integrations/hooks_controller.rb
  • integrations/hook.rb
  • inbox_bot_status.rb
  • CWE-639 · CWE-863

License

GNU Affero GPL v3.0. See LICENSE. Loopback lab only. No warranty.

Abraxas Labs [email protected]

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →