CVE-2026-73481 in phpList exposes a CSRF bypass in the bounce rule deletion endpoint, but the real problem runs deeper than one broken endpoint. The verifyCsrfGetToken function accepts an enforce=false parameter, and when enforce=false is passed, the function returns true (verification passed) regardless of whether a valid token was provided. The bounce rule deletion code calls this function with enforce=false and provides no 'tk' parameter—so the CSRF check always passes, not because protection is absent, but because protection is conditionally disabled. This is structurally worse than no CSRF protection at all: automated security scans will report CSRF protection as implemented for this endpoint, code reviews will see the verifyCsrfGetToken call and move on, and defenders will have false confidence in their coverage. The vulnerability lives inside the security model itself, invisible to tools that check for the presence of controls rather than their conditional absence. Additionally, this endpoint accepts GET requests for deletion, which means the vulnerable URL persists in server access logs, proxy logs, browser history, and Referer headers—creating persistent exfiltration risk without requiring user interaction beyond initial page load. If you deploy phpList, search your codebase immediately for other calls to verifyCsrfGetToken with enforce=false—this is likely not an isolated instance. Treat enforce=false in security validation functions as a prohibited pattern going forward, not just a bug to patch. The EPSS score of 0.00149 likely reflects limited external awareness of phpList admin panel exposures rather than genuine rarity of exploitable instances.
CVE-2026-73481
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedphpList before 3.7.0-RC5 fail to enforce CSRF token validation on the bounce rule deletion endpoint (bouncerules.php / bouncerule.php). The deletion is performed via a GET request (?page=bouncerules&del=N), and the central CSRF check (verifyCsrfGetToken) is invoked with enforce=false, so it only validates the token when a 'tk' parameter is present. A remote attacker can trick an authenticated administrator into loading a crafted URL (e.g., embedded in an image tag) to delete arbitrary bounce rules from the phplist_bounceregex table without a valid CSRF token.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisThe application can't tell whether a state-changing request was genuinely intended by the user, so an attacker can trick a logged-in victim's browser into making it. That can transfer funds, change settings, or create accounts silently. Remediation is anti-CSRF tokens — or equivalent same-site protections — on every state-changing request.
General guidance for the cross-site request forgery (csrf) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedphpList 3.7.0-RC5 or later stable release
- Backup the current phpList installation and database before proceeding with any changes
- Download phpList 3.7.0-RC5 or a later stable release from the official phpList repository (github.com/phpList)
- Replace the existing phpList files with the new version, preserving configuration files and any custom templates
- Verify the bounce rule deletion endpoint (bouncerules.php) now properly enforces CSRF token validation
- Confirm the application functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,000. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-73481 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesCVE-2026-73481 in phpList exposes a CSRF bypass in the bounce rule deletion endpoint, but the real problem runs deeper than one broken endpoint. The verifyCsrfGetToken function accepts an enforce=false parameter, and when enforce=false is passed, the function returns true (verification passed) regardless of whether a valid token was provided. The bounce rule deletion code calls this function with enforce=false and provides no 'tk' parameter—so the CSRF check always passes, not because protection is absent, but because protection is conditionally disabled. This is structurally worse than no CSRF protection at all: automated security scans will report CSRF protection as implemented for this endpoint, code reviews will see the verifyCsrfGetToken call and move on, and defenders will have false confidence in their coverage. The vulnerability lives inside the security model itself, invisible to tools that check for the presence of controls rather than their conditional absence. Additionally, this endpoint accepts GET requests for deletion, which means the vulnerable URL persists in server access logs, proxy logs, browser history, and Referer headers—creating persistent exfiltration risk without requiring user interaction beyond initial page load. If you deploy phpList, search your codebase immediately for other calls to verifyCsrfGetToken with enforce=false—this is likely not an isolated instance. Treat enforce=false in security validation functions as a prohibited pattern going forward, not just a bug to patch. The EPSS score of 0.00149 likely reflects limited external awareness of phpList admin panel exposures rather than genuine rarity of exploitable instances.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-73481 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data