Zenphoto needs the data directory checked before the admin page
Zenphoto is a self-hosted media gallery and content-management system. Its public gallery is expected to be visible, while its administrative pages and configuration data require a separate trust decision. A count-only search can show that the product name appears on the internet. It cannot show whether the sensitive data directory is protected or whether an administrator account is properly separated.
The ZoomEye query was executed on 2026-11-20 at 04:45 CST with page 1, pagesize 1, and sub_type=all. app="Zenphoto" returned 54 matches. title="Zenphoto" returned 15 matches. The two small counts describe index matches for the exact strings, not a confirmed count of galleries or a count of vulnerable installations.
The project's user-rights documentation describes multiple administrative capabilities. A user with file access can use the file manager, while full administrator rights can manage users and settings. That is a meaningful distinction. A gallery owner may need to upload and arrange media without being able to change authentication or install themes and plugins.
Protect the data folder
Zenphoto's setup and configuration material identifies zp-data as a sensitive directory. The installer checks whether its permissions are restrictive and warns when the data folder is exposed. Configuration, logs, and internal state should not be readable through the web server. Put the directory outside the document root where the deployment supports it, or deny direct web access with the web server's configuration.
Review the admin login path separately from the public gallery. An administrator page can be protected by a strong account but still be exposed to credential stuffing and bot traffic. Restrict it to a management network or an authenticated reverse proxy when possible. Enable logging for login failures and review whether a password reset path can be reached by an unauthenticated visitor.
Themes and extensions are code. A theme that is editable from the admin interface can become a write-to-execution path if the web server can execute files under the theme directory. Keep the theme directory read-only in production where possible, deploy reviewed versions through the normal release process, and disable installation of unreviewed packages.
Review rights and public roles
Create a role that can upload and edit gallery content without full administrator rights. Verify that it cannot change users, security settings, or plugin configuration. Test whether a public visitor can enumerate albums that are not intended to be public. A gallery may use a shared link or a guest role, and those paths need their own tests.
The data directory and the admin role answer different questions. The first asks whether configuration can be read or modified through the web server. The second asks which authenticated person can change the site. A count query cannot answer either question, but the small title count can help an owner find pages that claim to be Zenphoto deployments and compare them with internal inventory.
The practical output is a checklist: data folder denied, admin route restricted, roles separated, themes controlled, plugin inventory current, and backups tested. The ZoomEye result is a starting point for that review, not a severity verdict.

