Published research · anonymized environment

The integration was trusted. Its permissions needed a closer look.

Two investigations followed the boundary between an application and its customer-data and support platforms. The weakness lay in the way the integrations were configured and exposed.

Research focus
Third-party integration configuration
Platforms involved
Salesforce · Zendesk
Publication
15 December 2025
Evidence
Catchify’s published technical article

These were integration misconfigurations in the environments investigated. The research does not identify product vulnerabilities in Salesforce or Zendesk.

Business workflows extend beyond the core application.

CRM and support integrations can carry personal information, documents, and the authority to communicate with customers. The investigation followed those connections to understand where an ordinary or unauthenticated user could reach a more privileged capability.

Salesforce: exposed data access

The article describes a community-specific Aura route that exposed internal user information. It also documents accessible document-download paths with insufficient access controls.

Zendesk: a privileged browser token

An embedded support component made a privileged authorization token visible in browser traffic. The researchers checked the token’s authority against the support API.

Follow what the application actually trusts.

  1. Map the integration surface

    Follow routes, embedded components, and browser requests to identify the connected services and the context in which they are called.

  2. Check the authorization boundary

    Compare the user’s intended permissions with the data and operations exposed by each integration, including routes outside the most obvious entry point.

  3. Validate and document impact

    Establish what the exposed access permits and document the evidence needed to explain its significance to the owner.

Sensitive data and support authority.

The published article reports access to sensitive Salesforce documents and extensive Zendesk user information. It also describes administrative access across connected support channels, including email, WhatsApp, and X.

The public article is the record of these observations. This case summary does not claim a completed client retest or quantify a commercial outcome.

THE PRACTICAL LESSON

Test the privilege behind the workflow.

A feature can look ordinary in the interface while using a much more powerful identity behind the scenes. Include that trust relationship in the assessment scope.

Reduce what the integration can expose.

These are defensive recommendations derived from the failure modes described, not a claim that a particular customer implemented them.

  • Review guest and community permissions, object access, and document sharing. Enforce access checks for each request and object.
  • Keep privileged service credentials out of browser code and requests. Route privileged operations through a server-side service with appropriate authorization.
  • Rotate exposed credentials and reduce integration permissions to the functions the workflow actually needs.
  • Review available logs for unexpected access, and include connected support channels in the incident assessment.
  • Retest the original access paths and neighboring workflows after remediation, including negative checks for unauthorized users.

Sources & further reading

What do your integrations trust?

Include CRM, support, identity, and other connected services when you scope your next assessment. Ask us for a relevant client example if you need one for your review.