Liferay Exposure Crosses Virtual Instances and Role Scopes
Liferay deployments often combine portals, sites, accounts, users, and custom applications in one installation. Public discovery needs to respect that internal partitioning.
Counts and confidence
On 2026-11-20, ZoomEye returned 2 matches for app="Liferay" and 4,242 for title="Liferay" with sub_type=all, page 1, and pagesize 1. The sparse application fingerprint is not a reliable population estimate. The title count is the broader discovery signal and needs manual validation.
Neither result proves a vulnerable version or an exposed administrative interface.
Isolation model
Liferay documents virtual instances as separate data and configuration planes within a shared installation. Regular roles can operate across a virtual instance, while site roles and asset permissions operate within narrower scopes. This is the core review distinction.
An administrator who can view users globally has different authority from a site administrator. A role that appears harmless at site scope can become sensitive when paired with a global user or organization permission.
Review priorities
For each candidate, identify all virtual instances and their domains. Review regular roles, site roles, account roles, and asset-level permissions separately. Check default admin accounts and custom roles with user or permission-management capability.
Inspect custom applications and low-code objects for permission gaps. Confirm that authenticated API paths enforce the same scope as the web interface.
Monitoring
Track virtual-instance creation, changes to authentication, global role assignments, and resource-permission changes. Alert when a site role is recreated as a regular role with broader scope without an approved design.
ZoomEye identifies public portal surfaces. Liferay's own role and instance model determines whether a discovered surface exposes data or administration beyond policy.
Top comments (0)