DEV Community

StarkMan
StarkMan

Posted on

Mealie Household Permissions Can Hide Behind a Public Recipe Page

Mealie Household Permissions Can Hide Behind a Public Recipe Page

A public recipe page can be intended and still reveal more about a household than the owner expects. Mealie combines user accounts, groups, households, API tokens, webhooks, notifiers, and public access settings. The public-facing recipe path and the administrative endpoints are different surfaces, but they can share the same deployment and configuration.

Mealie's permissions documentation separates administrator access, invitation generation, group management, household management, and the ability to organize group data. The Manage household permission covers household settings, notifiers, and webhooks. A user with that permission can change an outbound integration even if they cannot manage the whole group.

Inventory the household boundary

Record which users belong to each group and household, which permission categories they have, and whether public recipe access is intentional. Identify the owner of each API token and the integration that uses it. A long-lived token created in the user profile inherits the user's access, so the token review should start with the human account, not with the token label.

Keep administrative users separate from accounts used for recipe browsing or family members. If the deployment supports OIDC or another centralized identity provider, map the group and admin claims deliberately. A broad default group can give new users more household visibility than an invitation workflow intended.

Review public access as a product decision

Public recipe access should be an explicit publishing choice. Check which recipes, images, comments, or metadata are visible without authentication. Confirm that public endpoints do not expose meal plans, shopping lists, user profiles, or notifier configuration. If the service is intended for a private household, block the public path at the reverse proxy or disable it in the application.

Review webhooks and notification destinations. A webhook URL can contain a secret token or point at a chat service. A household manager who can edit it may be able to redirect notifications or send crafted content. Test whether an ordinary user can list or change those settings.

What the ZoomEye observation shows

The query used sub_type=all, page 1, and page size 1. app="Mealie" returned no matches, title="Mealie" returned 4,104, and http.body="Mealie" returned 15,361. The body result is broad and should be treated as a discovery set, not a count of private households. The title result can help find branded deployments, but ownership must still be established before any interaction.

For an owned server, compare the public recipe URL with the administrative URL and the container network exposure. A reverse proxy can publish one route while leaving the API reachable on another hostname or port.

Test the permission boundaries

Use test accounts to confirm that a household manager cannot change group-wide settings, that an ordinary user cannot modify webhooks, and that a revoked token stops working. Test invitation links, public recipe links, and password reset flows from an unauthenticated client. Capture the status codes and audit events.

Mealie's security depends on the difference between sharing a recipe and exposing a household. Keep that difference visible in configuration, permissions, and monitoring.

References

Top comments (0)