Cypht's 157 title matches sit in front of multiple linked mail accounts
A webmail aggregator can hold sessions for several unrelated mail accounts at one time. That makes account linking, session protection, and server-side HTML handling part of the same security boundary. A count-only ZoomEye probe found 157 assets with title="Cypht" and zero with app="Cypht". The title count identifies candidate deployments. It does not show which accounts, providers, or two-factor settings are configured on each host.
Cypht's introduction describes a server-side modular aggregator for multiple email accounts. The security overview describes encrypted session data, a minimal web root, CSRF protection, two-factor authentication, and HTML filtering before message rendering. The account-setup guide covers incoming and outgoing mail-server configuration and OAuth clients for providers such as Exchange and Gmail.
The ZoomEye result in context
The SDK queried app="Cypht" and title="Cypht" with sub_type="all", page 1, and page size 1 at 08:43 Asia/Shanghai on 17 November 2026. The app query returned 0 and the title query returned 157. A title match may be a login page, an account setup page, documentation, or an error response. The total is a count for the exact title query, not a count of compromised mailboxes.
Because no application fingerprint appeared, owners should not treat the zero as an all-clear. Confirm the login flow and product behavior before assigning the host to an organization.
Review the linked-account boundary
Each linked mailbox is a separate external authority. Inventory provider, account owner, authentication method, OAuth client, refresh token, and server configuration. A user who can add an account may be able to make the server contact an unintended mail service or disclose credentials during setup. Restrict account creation to trusted administrators where the deployment model supports it.
The session must not expose another user's linked accounts. Test logout, session invalidation, password change, and two-factor reset. Verify that a removed account cannot still send mail or access cached messages. If PHP session storage is shared, review its permissions and isolation from other applications on the host.
Treat rendered mail as untrusted
External HTML, remote images, and attachments are hostile input. Keep HTML filtering enabled, block remote resources by default, and verify that a message cannot invoke privileged application actions through a crafted link or form. Attachment previews should use a separate rendering boundary and should not expose server files.
A Cypht inventory should record the host, owner, linked providers, OAuth applications, session storage, 2FA policy, and last update. ZoomEye can show public candidates. The mail-account boundary and the session store remain owner-controlled,
Top comments (0)