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

CVE-2025-31588

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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 elfsight Elfsight Testimonials Slider elfsight-testimonials-slider allows Cross Site Request Forgery.This issue affects Elfsight Testimonials Slider: from n/a through <= 1.0.1.

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 Elfsight Testimonials Slider WordPress plugin (versions <= 1.0.1) allows attackers to trick authenticated administrators or users into performing unintended actions such as modifying plugin settings or submitting content through forged requests.

MitigationImplement anti-CSRF tokens (nonces) in all form submissions and AJAX actions within the plugin, and verify these nonces on the server side before processing any state-changing 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
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

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. Identify the installed plugin version
    Navigate to the WordPress admin dashboard, go to Plugins > Installed Plugins, locate 'Elfsight Testimonials Slider', and check the version number displayed below the plugin name
    Affected if The displayed version is 1.0.1 or lower (any version up to and including 1.0.1)
  2. Confirm the plugin is active
    In the same Plugins screen, verify that the 'Elfsight Testimonials Slider' plugin shows as 'Active'
    Affected if The plugin is active and the version is 1.0.1 or lower
  3. Check for state-changing admin pages
    Access the plugin settings page (usually under 'Settings' or a dedicated menu item for Testimonials Slider in the WordPress admin sidebar) and identify any forms that modify plugin settings, add/edit testimonials, or change configuration
    Affected if The plugin has settings or content submission forms accessible to authenticated administrators or users
  4. Inspect form submissions for CSRF protection
    View the page source of the plugin settings or testimonial submission forms. Look for a hidden input field named 'nonce', '_wpnonce', or similar, or a JavaScript variable containing a nonce value, within the form tags
    Affected if No nonce field (such as wp_create_nonce, _wpnonce, or similar) is present in any plugin-related form that modifies settings or submits content

The environment is affected if the Elfsight Testimonials Slider plugin is installed and active at version 1.0.1 or lower, and the plugin's settings or content forms lack CSRF token (nonce) 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) in all form submissions and AJAX actions within the plugin, and verify these nonces on the server side before processing any state-changing requests.

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-31588 — 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-31588 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