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

CVE-2025-31616

HIGH · 7.1 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 →
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 AdminGeekZ Varnish WordPress varnish-wp allows Cross Site Request Forgery.This issue affects Varnish WordPress: 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in AdminGeekZ Varnish WordPress plugin (varnish-wp) versions through 1.7 allows remote attackers to trick authenticated administrators into performing unintended actions (likely modifying varnish configuration settings) by embedding malicious requests in external sites.

MitigationImplement anti-CSRF tokens (WordPress nonces) on all state-changing forms and AJAX endpoints, validate Referer/Origin headers, and update to version 1.8 or later if available.

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. Locate the varnish-wp plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'varnish-wp' or 'admin-geekz-varnish'. If using WP-CLI, run: wp plugin list --name='varnish'
    Affected if The varnish-wp plugin folder exists in the WordPress installation
  2. Identify the installed version
    If the plugin folder exists, check the main plugin PHP file (e.g., varnish-wp.php) for the 'Version' header in the plugin comment block. Alternatively, use WP-CLI: wp plugin get varnish-wp --format=json
    Affected if The reported version is 1.7 or lower (any version 'through 1.7' per the CVE)
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm varnish-wp shows as 'Active', or use WP-CLI: wp plugin is-active varnish-wp
    Affected if The plugin is activated and accessible to administrators
  4. Confirm admin access to varnish settings
    Log into WordPress as an administrator and navigate to the plugin settings page (typically under Settings > Varnish or a similar AdminGeekZ menu). Verify the configuration forms are accessible.
    Affected if The varnish configuration interface loads and accepts administrator input

You are affected if the varnish-wp plugin is installed with version 1.7 or lower and is active, allowing an authenticated administrator to access the varnish configuration settings.

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 (WordPress nonces) on all state-changing forms and AJAX endpoints, validate Referer/Origin headers, and update to version 1.8 or later if available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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