DEV Community

yutianle
yutianle

Posted on

Elgg by Title: Access Collections Define Where a Social Site Leaks

Elgg by Title: Access Collections Define Where a Social Site Leaks

Elgg is a self-hosted framework for social applications. A count-only ZoomEye observation returned 74 matches for title="Elgg", 0 for app="Elgg", and 1,987 for http.body="Elgg". The title set is small enough to review by owner, while the design of the product makes the access model more important than the count.

Elgg documentation describes an access identifier on entities and annotations. Built-in modes include private, logged-in, and public, and administrators can create user-defined access collections. Database-layer retrieval functions are designed to return only content visible to the current user. The product also documents gatekeeper functions and pluggable authentication handlers.

Inventory the audience model

For each owned social site, list the access collections and the users or groups they include. Confirm which content types can be public, logged in, or restricted. Then review plugins that register actions, modify permissions, or introduce new content types.

The administrative hardening guide also recommends protecting upgrade and cron URLs with unique tokens and limiting direct access to sensitive directories. Those are supporting controls around the same question: which unauthenticated or low-privilege request can reach data or an action?

Tests that matter

  • Fetch an entity as its owner, as a member of its access collection, and as an unrelated user.
  • Test public and logged-in content after changing the site access policy.
  • Review admin-only actions and plugin-defined public actions.
  • Confirm that upgrade and cron controls are enabled where the deployment supports them.
  • Check third-party plugins for custom permission callbacks.
  • Verify that profile data and user directories follow the intended visibility policy.

What the count cannot decide

The title query does not identify the configured access collections or prove that any content is public. The body count includes references and documentation. A deployment may have a visible public front page while most content remains restricted, or the reverse.

Elgg's data model makes access a property of each object. That is powerful, but it requires an operational process for templates, groups, and plugins. The owner should be able to explain why a piece of content is public, not only that the application rendered a login screen.

Method and limits

The observation used sub_type=all, page 1, and page size 1 on 2026-11-17. Matching assets are not confirmed vulnerable systems.

References

Top comments (0)