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

CVE-2025-23880

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 anmari amr personalise amr-personalise allows Cross Site Request Forgery.This issue affects amr personalise: from n/a through <= 2.10.

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 amr-personalise plugin allows attackers to trick authenticated users into performing unintended actions. The plugin lacks proper anti-CSRF token validation on state-changing operations, enabling malicious requests to be processed when a logged-in user visits a crafted attacker-controlled page.

MitigationImplement anti-CSRF tokens (nonces) on all forms and AJAX endpoints that perform state-changing operations, validate these tokens server-side, and configure SameSite cookie attributes to prevent cross-origin cookie transmission.

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 checks

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

  1. Confirm amr-personalise plugin installation
    Locate the plugin directory in your WordPress installation (typically wp-content/plugins/) and verify the amr-personalise folder exists. Check for the main plugin file (usually amr-personalise.php)
    Affected if The plugin folder or main file is present in the plugins directory
  2. Identify the installed plugin version
    Open the main plugin file and locate the version comment in the plugin header (comment block at the top containing 'Version: x.x.x'). Compare this version to any known affected version ranges
    Affected if The installed version falls within an affected version range (if such ranges are published) or is unknown/unpatched
  3. Audit state-changing forms for nonce tokens
    Examine PHP files in the plugin that handle form submissions (POST requests) and check if each form includes a nonce field (wp_create_nonce or similar) and validates it with wp_verify_nonce before processing
    Affected if Forms that modify data (settings, user preferences, database entries) lack nonce validation code or contain only minimal/tamperable validation
  4. Audit AJAX endpoints for CSRF protection
    Search for add_action('wp_ajax_') and add_action('wp_ajax_nopriv_') calls in the plugin. For each callback, verify it validates a nonce via wp_verify_nonce or check_admin_referer before performing state-changing operations
    Affected if AJAX handlers that modify data do not validate nonces or accept requests without token verification
  5. Check cookie SameSite attribute configuration
    Inspect the plugin code for calls to setcookie or headers that set session cookies. Verify SameSite attribute is set to 'Strict' or 'Lax', not 'None' without Secure flag, to help prevent cross-origin cookie transmission
    Affected if Cookies are set without SameSite attribute or with SameSite=None without Secure=True, increasing CSRF exploitability

You are affected if the amr-personalise plugin is installed and its state-changing operations (forms or AJAX endpoints) lack proper nonce validation and cookie SameSite protection.

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 anti-CSRF tokens (nonces) on all forms and AJAX endpoints that perform state-changing operations, validate these tokens server-side, and configure SameSite cookie attributes to prevent cross-origin cookie transmission.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23880 — 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-23880 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