Piranha CMS: 36 application matches, 81 titles, and a production account boundary
Piranha CMS: 36 application matches, 81 titles, and a production account boundary Piranha CMS is a .NET content platform that can run as an integrated CMS or as a headless API. Its manager interface uses claims and pol
Piranha CMS: 36 application matches, 81 titles, and a production account boundary
Piranha CMS is a .NET content platform that can run as an integrated CMS or as a headless API. Its manager interface uses claims and policies to decide which functions a user can access. A small public footprint is useful because it makes owner review practical, but the same small deployment may be the one holding an internal site or a public API.
On 2026-11-17, a bounded ZoomEye SDK query used sub_type=all, page 1, and pagesize=1. app="Piranha CMS" returned 36 total matches at 2026-11-17T06:55:16.766541+08:00. title="Piranha CMS" returned 81 total matches at 2026-11-17T06:55:17.869994+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 app query returned 36 and the title query returned 81. The application result is a product-specific lead. The title result adds candidates and possible name collisions. Neither number establishes default credentials, vulnerable code, or an exposed manager. A review should turn each confirmed host into a deployment question about the manager, the public site, and any REST API package.
Claims and roles define the manager
Piranha's authentication documentation describes a claims-based model with roles that grant access to claims. The manager claims include access to the manager interface and permissions for content actions. The documentation also describes development and production authentication packages. A deployment should use a production identity path, name the administrator roles, and confirm which claims each role carries for pages, posts, media, and settings.
A default development account is a deployment hazard when it survives into production. The official repository advises changing the development credentials and password policy for production. The review should verify that the default user is removed or replaced, that password and account recovery are controlled, and that any sample account is not shared across environments.
Check the headless path
The Piranha package documentation describes a REST API package for using the platform as a headless CMS. That path may be served by the same host as the public site or by a separate application. Inventory the API base path, authentication policy, content scopes, and CORS settings. A public read API can be intentional; a write endpoint should require a named role and should be covered by the same owner as the manager.
The manager is not necessarily exposed on the same hostname as the public front end. A custom deployment may have a separate admin domain behind an identity-aware proxy. The external title query can find candidates, but the owner should confirm which host serves the manager and which host serves the API. Do not attempt to enumerate administrative paths beyond the documented entry point.
Use the counts to set review order
Start with application matches because they have the strongest target-specific signal. For each, collect host, certificate, title, response status, and owner. Then compare the title list and identify hosts that appear in both sets. A host that appears in the application query and the title query is a higher-confidence candidate than a title-only mention. A title-only host may still be a real deployment, but it needs stronger confirmation.
Record the exact dorks, query time, sub_type=all, and page size. A later review should not compare a new title count with an old application count and call the difference growth. Keep the two series separate.
Decide what the public surface should be
Public content delivery, preview, manager, and API are four surfaces. They may share code but not policy. A deployment should define which surfaces are allowed from the internet and which are reachable only through a gateway. The manager path should not be public merely because the public website is. A preview host should not render unpublished material for anonymous users. An API should not use a shared administrator credential for a read-only integration.
Piranha's public population is small enough to review carefully. The 36 application matches are a better starting set than 36 inferred vulnerabilities. Treat the manager account and API permissions as the security decisions, and the measurement as the map.
References
[1] ZoomEye application query. https://www.zoomeye.ai/searchResult?q=YXBwPSJQaXJhbmhhIENNUyI%3D
[2] ZoomEye title query. https://www.zoomeye.ai/searchResult?q=dGl0bGU9IlBpcmFuaGEgQ01TIg%3D%3D
[3] Piranha CMS authentication. https://piranhacms.org/docs/v7/architecture/authentication
[4] Piranha CMS packages and REST API. https://piranhacms.org/docs/v7/basics/packages
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.