CVE-2025-26572
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in jesseheap WP PHPList phplist-form-integration allows Cross Site Request Forgery.This issue affects WP PHPList: from n/a through <= 1.7.
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 analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP PHPList plugin (version <= 1.7). The plugin fails to implement proper anti-CSRF tokens on state-changing operations, allowing authenticated users to be tricked into performing unintended actions via malicious requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm WP PHPList plugin is installedLocate the wp-phplist or phplist plugin directory in wp-content/plugins/ and identify the main plugin file (usually phplist.php or wp-phplist.php)Affected if Plugin directory exists in the WordPress plugins folder
-
Determine installed plugin versionOpen the main plugin PHP file and locate the version comment in the file header, typically found in the plugin comment block with 'Version: x.x'Affected if Version number is 1.7 or lower
-
Identify state-changing operations in the pluginSearch the plugin PHP files for forms with method="post" or "get", and AJAX handlers (wp_ajax_ hooks) that perform database writes, settings changes, or subscriber managementAffected if Plugin contains forms or AJAX endpoints that modify data
-
Verify nonce implementation on formsInspect all <form> tags in the plugin for the presence of wp_nonce_field() or similar WordPress nonce functions, and check that admin.php?action= links include _wpnonce parametersAffected if Forms or action links lack nonce field generation code
-
Verify nonce verification in request handlersCheck the PHP code handling form submissions and AJAX calls for check_admin_referer() or wp_verify_nonce() calls before executing state-changing logicAffected if Request handlers do not verify nonce tokens before processing
Environment is affected if the WP PHPList plugin is installed at version 1.7 or lower AND the plugin's forms or AJAX endpoints lack nonce field generation and verification.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement WordPress nonces (anti-CSRF tokens) for all forms and AJAX endpoints, and verify these tokens on the server side before processing any state-changing requests.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26572 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26572 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
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
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