Summary
A cross-site request forgery vulnerability in phpList allows an attacker to abuse a logged-in administrator's browser to submit the mass subscriber removal form without a valid CSRF token. If an administrator visits a crafted page while authenticated, arbitrary subscriber addresses may be deleted and blacklisted without additional authentication verification.
Affected context
The issue occurs in phpList deployments where the mass subscriber removal form handler accepts requests without properly validating a CSRF token. It becomes risky when an administrator is authenticated in the same browser and can be induced to load attacker-controlled content while their session remains active.
Exploit preconditions
- Attack surface: The mass subscriber removal form handler
- Required access: A victim administrator must be authenticated to phpList
- Trigger point: A crafted page or request causes the victim's browser to submit the removal action
- Why exploitation is possible: The handler does not reliably verify a request-specific CSRF token or equivalent origin control before processing the action
Why this happens
The vulnerability results from insufficient CSRF protection on a state-changing administrative request. When a server accepts browser-submitted actions based primarily on an existing session, without validating an unpredictable token tied to the intended form and session, an external site may cause the browser to send an unauthorized request. This behavior maps to CWE-352: Cross-Site Request Forgery.
Potential impact
- Unauthorized deletion of subscriber records
- Blacklisting of arbitrary subscriber addresses
- Loss of mailing-list data and administrative control over subscriptions
- Operational disruption or reputational harm
General mitigation guidance
Mitigation generally focuses on enforcing CSRF defenses for every state-changing administrative action.
Common defensive patterns include:
- Requiring unpredictable, session-bound CSRF tokens on the form and server-side handler
- Rejecting requests with missing, invalid, expired, or mismatched tokens
- Applying same-site cookie protections and appropriate origin or referer validation as defense in depth
- Using explicit confirmation and least-privilege administrative permissions for destructive operations
- Reducing reliance on ambient browser credentials and avoiding state changes through cross-origin-friendly request methods
How teams detect issues like this
Organizations commonly identify CSRF risks through:
- Static analysis checks for state-changing handlers that lack token validation
- Code review searches for administrative POST or action endpoints without CSRF middleware
- Dynamic testing that submits requests with missing, invalid, or cross-session tokens
- Policy enforcement requiring centralized CSRF protection for all mutating routes
- Review of audit logs for subscriber-removal actions lacking expected user interaction or valid request metadata

