Crater invoicing controls need a tenant and API-token review
Crater is an open-source invoicing application for expenses, payments, estimates, and customer records. A public login page can look ordinary while the application behind it holds customer identities, billing history, bank details, and exported financial records.
The ZoomEye observations from 2026-11-15 used page 1, pagesize 1, and sub_type=all. app="Crater" returned 1, title="Crater" returned 1,634, and http.body="Crater Invoice" returned 13. The one application match and the broader title match deserve different interpretations. Confirm the product and the deployment before using either as an asset count.
Define the account boundary
Start with the organization or company context configured in the installation. Review who can invite users, change company information, edit invoices, issue payments, and export records. A support role should not automatically gain the ability to change bank details or purge records.
Document the API clients and automation accounts separately from human users. An API token may have been created for an integration and forgotten after the integration was replaced. Record its owner, creation date, scope, last use, and revocation path.
Protect financial records and templates
Invoice templates, email settings, storage configuration, and backups can contain secrets or a complete copy of customer data. Restrict administrative pages to a management network where practical. Use HTTPS and protect the application secret values in the deployment configuration.
For a discovered instance, compare the title with the application and the login response. Do not assume that a Crater title match is an exposed finance system. It may be documentation, a demo, or a page that mentions the product.
Test a realistic role matrix
Use two users with different roles. Try to view another company's data if the deployment supports multiple companies or workspaces. Try to create an invoice, change payment settings, invite a user, and use an API token. Verify that a removed user cannot continue with an old session or a cached token.
Record the effective company scope, role, and action. A single successful login test is too weak for a system that can send invoices and change payment instructions.
Crater exposure is a financial-data boundary problem. The useful inventory connects each instance to its company owner, user roles, API clients, and recovery plan.