Reaction Commerce: 80 body signals and a GraphQL admin that should be reviewed as an API
Reaction Commerce, also documented as Mailchimp Open Commerce, is an API-first ecommerce platform built around a GraphQL API, a separate admin application, a storefront, and identity services. The architecture is distributed even when the user experiences one storefront.
A count-only ZoomEye query on 17 November 2026 at 02:50 Asia/Shanghai found 80 assets with http.body="Reaction Commerce", 1 with title="Reaction Commerce", and no app="Reaction Commerce" matches. All requests used sub_type=all, page 1, and pagesize=1. The body count is a broad discovery signal; the single title and zero application matches show why product naming and deployment customization complicate internet measurement.
Treat the admin as an API client
The Admin UI is not the only way to change products, orders, accounts, or shop settings. It calls the GraphQL API, and other integrations may call the same schema. A security review should therefore test authorization at the API resolver or service layer, not only at the rendered interface.
The platform documentation describes a Reaction API, Reaction Admin, an example storefront, and Reaction Identity with Hydra in the development platform. Those components can run on separate hosts and use different credentials. Identify which proxy route exposes the storefront, admin, GraphQL API, and identity endpoints, and whether each one has the same authentication boundary.
A public GraphQL endpoint may support introspection or schema discovery depending on configuration. Schema visibility is not automatically a vulnerability, but it can help an unauthorized user understand available queries and mutations. The decisive question is whether each operation enforces account, shop, and role scope.
Review the identity path
Start with the identity provider and Admin authentication. Confirm which service issues tokens, which audience and scopes are accepted, and how account status changes propagate to existing sessions. Review the proxy configuration around Reaction Identity and Hydra rather than assuming the application controls every route.
Next, map shops and accounts. Determine which users can become administrators, how invitations are handled, and whether a storefront customer can access an Admin mutation. Check the service accounts used by payment, shipping, inventory, and catalog integrations. A service token with broad shop access should be isolated from the public storefront.
GraphQL authorization should be tested with multiple identities: anonymous, customer, support user, shop administrator, and system integration. For each mutation, verify both object ownership and operation permission. Do not rely on the Admin UI hiding a button.
Discovery and validation
The body query is:
http.body="Reaction Commerce"
Use it to find pages that mention the platform, then confirm whether the host is a storefront, admin, API, documentation site, or partner page. The product may be branded as Mailchimp Open Commerce, so a single name can miss deployments. A low count should not be interpreted as proof of low adoption.
Collect the hostname, public components, GraphQL endpoint, identity provider, storefront version, admin version, and ownership. Review the reverse proxy paths as one system. A route that bypasses the expected Admin ingress may still reach the API.
ZoomEye's contribution is the public body signal that connects the distributed components back to a product family. The security result comes from testing the GraphQL and identity boundaries directly, with each request mapped to an account, shop, and permitted operation.
Top comments (0)