/

CVE-2026-73482

Severity:

HIGH RISK

(8.1)

CSRF (CWE-352) in phpList Administrator Deletion Action

CVE-2026-73482

Deferred

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352

Impact:

Unauthorized administrator account deletion

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

phpList before 3.7.0-RC5 contains a cross-site request forgery vulnerability in the administrator deletion function. An attacker may cause a logged-in super-administrator to submit an unintended request that deletes another administrator account when the action is exposed through an unauthenticated GET request.

Affected context

The vulnerability occurs in phpList's administrator management interface when the deletion action is reachable through a GET request and CSRF protection does not require a valid token. Risk is present when a super-administrator is authenticated in the same browser and can be induced to visit attacker-controlled content, such as a crafted link or embedded resource.

Exploit preconditions

  • Attack surface: The administrator management endpoint at lists/admin/admins.php
  • Required access: The victim must be logged in with super-administrator privileges
  • Trigger point: A request using the administrator deletion action and target account identifier
  • Attacker interaction: The victim must be induced to load attacker-controlled content or follow a crafted URL
  • Why exploitation is possible: The deletion request can be processed without requiring a valid CSRF token, allowing the browser to include the victim's authenticated session

Why this happens

The underlying flaw is a state-changing administrator action exposed through an unauthenticated GET request without effective request-origin verification. The central CSRF check is configured so that a missing token does not enforce rejection, allowing the request to proceed when the token parameter is absent. This maps to CWE-352: Cross-Site Request Forgery, where an application performs a privileged action based on a request that was not intentionally initiated by the authenticated user.

Potential impact

  • An attacker could delete non-self administrator accounts
  • Administrative access could be disrupted or reduced
  • The organization could lose authorized operators or recovery contacts
  • Follow-on account takeover or service disruption could become easier

General mitigation guidance

Mitigation generally focuses on ensuring that every state-changing administrative request requires strong proof of user intent.

Common defensive patterns include:

  • Requiring unpredictable, session-bound CSRF tokens for all state-changing actions
  • Rejecting requests when tokens are missing, invalid, expired, or associated with another session
  • Using POST or another non-idempotent method for destructive operations rather than GET
  • Applying centralized CSRF middleware consistently, without optional enforcement for privileged actions
  • Requiring explicit confirmation and appropriate authorization checks for administrator deletion
  • Limiting administrator privileges and adding recovery controls where possible
  • Using appropriate cookie protections and origin or referer validation as defense-in-depth

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis that flags state-changing operations reachable through GET requests
  • Code review checks for missing, optional, or bypassable CSRF validation
  • Testing that omits tokens and verifies that privileged requests are rejected
  • Dynamic testing of administrative actions with cross-origin request scenarios
  • Web application policies requiring CSRF protection and non-GET methods for destructive operations
  • Audit-log monitoring for unexpected administrator deletion events

Automated security review tools may help identify missing token checks, but authorization and workflow behavior should also be validated through targeted testing.

Sources

SourceLink
github.comgithub.com/phpList/phplist3/commit/5159c3ed33a5674a8169472b50d146d97f630746
github.comgithub.com/phpList/phplist3/issues/1117
github.comgithub.com/phpList/phplist3/pull/1121
github.comgithub.com/phpList/phplist3/releases/tag/v3.7.0-RC5
vulncheck.comvulncheck.com/advisories/phplist-rc5-cross-site-request-forgery-via-admins-php

Frequently asked

questions

Yes, within the browser-based attack model. The attacker generally does not need direct access to the phpList server, but must cause an authenticated super-administrator to load or follow attacker-controlled content.

No. The victim's active super-administrator session supplies the required authentication context, while the attacker supplies the crafted request.

Require a valid, session-bound CSRF token for every destructive action, reject missing or invalid tokens, and process administrator deletion through a non-GET request.

Enforce CSRF protection centrally and consistently, review all state-changing endpoints, prohibit destructive GET actions, and test privileged workflows against cross-origin requests.

Find out what's already
exploitable in your codebase.