WSO2 API Manager Counts Expose a Management Console Beside the Public API Plane
WSO2 API Manager Counts Expose a Management Console Beside the Public API Plane An API gateway is designed to be reachable. That makes product identification easy to confuse with intended exposure. WSO2 API Manager has
WSO2 API Manager Counts Expose a Management Console Beside the Public API Plane
An API gateway is designed to be reachable. That makes product identification easy to confuse with intended exposure. WSO2 API Manager has public-facing API and developer portal functions, but it also has a management console and administrative services that need a different review. A useful internet inventory separates those planes before it treats a match as a control-plane exposure.
What the measurement found
On 2026-11-19, a count-only ZoomEye SDK query with sub_type=all, page 1, and pagesize 1 returned zero matches for app="WSO2 API Manager". The same scope returned 398 matches for title="WSO2 API Manager" and 1,261 for http.body="WSO2 API Manager".
Those values describe indexed text and fingerprint labels at one collection time. They do not prove that a product is unauthenticated, that every matching host is a management console, or that all matches are production deployments. The zero app count is a warning against treating a broad body match as a product inventory. The title and body values are useful leads, not exposure claims.
Separate the product planes
WSO2 documentation describes the management console at /carbon and admin services under /services. The default management console HTTPS port is 9443 when the product has no port offset. The API publisher, developer portal, gateway, key manager, and traffic manager may use other ports and may be deployed on separate hosts.
A reviewer should capture the hostname, external URL, port, TLS certificate, response title, and the actual application path. Determine whether the reachable service is the public developer portal, the publisher, the management console, or an admin service. A screenshot of a product login page does not establish the same authority for every component.
Review credentials and network reach
The management console is an administrative identity path. Check whether it is bound only to an administration network, whether direct access is blocked at the load balancer, and which identity provider backs the login. Review default accounts, password rotation, session policy, and administrator role membership.
WSO2's production guidance recommends checking open ports and exposing only necessary services. It also identifies /carbon as the management console context and /services as the admin-services context. Use that guidance to build an explicit allowlist rather than a broad firewall rule for the whole product.
If single sign-on is used, verify that the management console and public portals do not share an authorization assumption. A user who can read an API definition should not automatically receive administrative access to the gateway.
Validate a candidate before acting
Start with the title and body candidates, then confirm the product through a controlled HTTP response and ownership record. Do not send credentials, attempt login, or enumerate administrative methods during discovery. Use an approved owner lookup and compare the observed endpoint with the deployment inventory.
If a host is unknown, ask the application owner to identify the component and deployment pattern. If it is a developer portal, record that it is public by design. If it is a management console, verify the network boundary and authentication path. If it is an unmanaged installation, treat the ownership gap as the first finding.
Keep the conclusion narrow
The measured counts show that WSO2 API Manager text is present in indexed web content while the application fingerprint did not match at that moment. That supports a careful discovery process. It does not support a claim that 398 systems are exposed consoles.
The defensible conclusion is simpler: identify the component, confirm the port and path, and review the authority behind the login. For an API platform, the public API door and the credential-bearing administration door should have separate inventories and separate access policies.
References
- Default Product Ports, WSO2 API Manager documentation. Retrieved 2026-11-18.
- Security Guidelines for a Production Deployment, WSO2 API Manager documentation. Retrieved 2026-11-18.
- Admin Services, WSO2 API Manager documentation. Retrieved 2026-11-18.
- ZoomEye counts:
app="WSO2 API Manager"0;title="WSO2 API Manager"398;http.body="WSO2 API Manager"1,261.sub_type=all, page 1, pagesize 1, observed 2026-11-19 UTC+8.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.