Summary
Admidio's RSS endpoints for forum and announcements modules may expose login-restricted content without requiring authentication. An unauthenticated attacker could retrieve forum topics and announcements, including titles, full post text, author names, and timestamps, when these endpoints are accessible.
Affected context
The issue occurs in Admidio deployments where the forum and announcements RSS endpoints remain publicly reachable even though the corresponding modules are configured for logged-in users only. The restriction may not be applied consistently to requests targeting the RSS feed paths, allowing sensitive community content to be returned without normal session checks.
Exploit preconditions
- Attack surface: Publicly reachable HTTP RSS endpoints
- Required access: No authenticated account may be required
- Trigger point: A GET request to the forum or announcements RSS endpoint
- Why exploitation is possible: Endpoint-level access control does not
consistently enforce the modules' login-only visibility settings
Why this happens
The underlying bug is an authorization enforcement gap in RSS endpoint handling. Access decisions applied to normal module pages are not reliably propagated to the corresponding feed handlers, so requests can receive content without an authenticated session. This behavior maps to CWE-200, Information Exposure, because information intended for restricted users is disclosed to an unauthorized party.
Potential impact
- Unauthenticated parties may read forum topics and announcements
- Private post text, author names, and timestamps could be disclosed
- Exposed content could reveal internal discussions or community activity
- Attackers could collect and index restricted information at scale
General mitigation guidance
Mitigation generally focuses on enforcing authorization consistently across
every representation of protected content, including RSS and API endpoints.
Common defensive patterns include:
- Applying the same login and module-visibility checks to RSS handlers as to
standard page requests
- Denying feed access by default when the underlying module requires login
- Centralizing authorization decisions instead of duplicating endpoint logic
- Limiting feed content and metadata to information explicitly approved for
public distribution
- Testing unauthenticated and low-privilege access paths in automated security
checks
- Following least-privilege principles for content visibility and feed
generation
How teams detect issues like this
Organizations can detect this class of issue through:
- Authorization tests that request RSS, API, and alternate content formats
without a session
- Static and code review checks for endpoint handlers that bypass shared
access-control middleware
- Dynamic testing of login-only modules through their corresponding feed URLs
- Monitoring web logs for repeated unauthenticated requests to RSS endpoints
- Policy checks requiring protected resources to enforce authorization across
all exposed representations
Automated security review tools may help identify missing access checks, but
endpoint-specific authorization tests remain important.

