dotCMS at 4,065 application matches and 4,781 titles needs a permission review
dotCMS at 4,065 application matches and 4,781 titles needs a permission review dotCMS combines a content repository, a back-end console, static and dynamic site delivery, REST and GraphQL APIs, and role-based permissio
dotCMS at 4,065 application matches and 4,781 titles needs a permission review
dotCMS combines a content repository, a back-end console, static and dynamic site delivery, REST and GraphQL APIs, and role-based permissions. The product can be used as a coupled CMS or as a headless content service. Its exposure question is therefore broader than a login page: which API paths can read or modify content, and which role or token authorises each call?
On 2026-11-17, a bounded ZoomEye SDK query used sub_type=all, page 1, and pagesize=1. app="dotCMS" returned 4,065 total matches at 2026-11-17T06:55:14.094586+08:00. title="dotCMS" returned 4,781 total matches at 2026-11-17T06:55:15.213914+08:00. The observed total is shown by the application query and the title query. The page size limited returned records, not the matched total.
The application and title counts are close: 4,065 and 4,781. That convergence makes the application query a stronger baseline than the two-field gap found in several other CMS products. It still does not prove that a host is vulnerable or that its administration path is public. It says the selected application fingerprint and the page title both identify a substantial population that merits grouped ownership review.
Role permissions cover content and API access
dotCMS documentation states that its permission system controls user access to content and back-end functionality through roles and individual user permissions. It also says permissions govern REST API access, including the use of API tokens. A token is therefore not a separate security universe. The effective authority comes from the token's user, roles, and object permissions.
Review roles, direct user permissions, and token ownership together. A role that can read a content type may still be unable to publish it, change a workflow, or alter a site. A front-end token should be limited to the content and routes that front end uses. A migration token should not retain global administration after the migration. The application owner should be able to list every token and explain why it exists.
Headless authentication changes the browser boundary
dotCMS supports trusted identity providers and headless authentication. A front end can authenticate a user through an identity provider and send a bearer credential to dotCMS, with dotCMS permissions deciding what the user can see. That is a useful model, but it requires the front end to handle the token correctly and the CMS to map the user to the correct role.
Check the role mapping rules, the session or token lifetime, and the logout or revocation path. A user who signs out of the front end should not retain a CMS API session indefinitely. A group mapping that grants DOTCMS_BACK_END_USER should be intentional and limited. A front-end user who only needs public content should not receive a back-end role through a broad default.
Group the discovered hosts
With thousands of title matches, per-host manual review is not the first step. Group by certificate, domain, hosting provider, response title, and redirect pattern. Ask the largest owners to confirm the dotCMS deployment and provide an internal inventory. Prioritise hosts that expose an API root, an authentication path, or a management route, but verify the path rather than assuming that the product name implies it.
The external query should not include a token, a user identifier, or a content identifier. Those values can turn inventory into data collection. Record only the host-level observation and the exact query scope. If a public response contains a credential, stop copying it and start the disclosure process with the owner.
Make a two-count baseline
Use both the app and title queries. A rise in app matches may reflect a fingerprint update or a new population; a rise in titles may reflect rebrands or marketing pages. Compare the two before attributing change. Re-run with the same sub_type=all, page size, and timestamp format. Keep the search links so another reviewer can inspect the exact query without reconstructing it from prose.
dotCMS is a good example of why a content platform count needs an authorization model. The API can deliver content, create it, or administer users depending on the token and role. The number tells you where to ask; the permission configuration tells you what the answer means.
References
[1] ZoomEye application query. https://www.zoomeye.ai/searchResult?q=YXBwPSJkb3RDTVMi
[2] ZoomEye title query. https://www.zoomeye.ai/searchResult?q=dGl0bGU9ImRvdENNUyI%3D
[3] dotCMS permissions. https://dev.dotcms.com/docs/manage/access-and-security/permissions/permissions
[4] dotCMS REST API authentication. https://dev.dotcms.com/docs/build/apis/api-basics/rest-api-authentication
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.