dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-64262

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in ramon fincken Auto Prune Posts auto-prune-posts allows Cross Site Request Forgery.This issue affects Auto Prune Posts: from n/a through <= 3.0.0.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress plugin 'Auto Prune Posts' (versions <= 3.0.0) allows attackers to execute unauthorized actions on behalf of an authenticated administrator. The plugin lacks proper anti-CSRF token validation on state-changing operations, enabling attackers to trick logged-in administrators into performing unintended actions like modifying post prune settings.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints within the plugin, and verify these nonces on all server-side processing to validate request authenticity.

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the Auto Prune Posts plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Auto Prune Posts' in the list of active plugins.
    Affected if The plugin appears in the list of installed plugins, regardless of activation status, indicating the plugin code is present in the environment.
  2. Identify the installed version number
    In the Plugins page, click on the plugin name or view details to locate the version number displayed in the plugin metadata.
    Affected if The version number is 3.0.0 or lower, placing it within the affected range.
  3. Inspect plugin PHP files for nonce implementation
    Access the plugin files via FTP or file manager in wp-content/plugins/auto-prune-posts/. Open the main PHP files (usually auto-prune-posts.php or similar) and search for nonce-related functions: wp_nonce_field, check_admin_referer, wp_verify_nonce, nonce_field, or verify_nonce.
    Affected if The plugin files contain no nonce validation functions, or the state-changing functions (settings save, post prune actions) lack calls to verify nonce tokens.
  4. Verify AJAX endpoints for nonce verification
    In the plugin files, locate any AJAX handlers (hooks like wp_ajax_). Examine whether these handlers call wp_verify_nonce or check_admin_referer before processing requests.
    Affected if AJAX endpoints that modify settings or perform prune actions do not validate nonces, allowing forged requests to execute.
  5. Examine forms for nonce field presence
    In the plugin admin settings page PHP files, locate form tags that submit state-changing data (such as settings forms). Check if these forms include a hidden input with name containing '_nonce' or '_wpnonce'.
    Affected if Forms that change plugin settings or post prune behavior lack embedded nonce fields, meaning the requests cannot be validated as originating from the legitimate admin session.

A user is affected if the Auto Prune Posts plugin version is 3.0.0 or lower AND the plugin code lacks nonce validation on its state-changing operations (settings updates, prune actions, or AJAX endpoints).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints within the plugin, and verify these nonces on all server-side processing to validate request authenticity.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64262 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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