LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31616: WordPress Varnish WordPress plugin <= 1.7 - CSRF to Stored XSS vulnerability

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-31616 affects the AdminGeekZ Varnish WordPress plugin, package varnish-wp, through version 1.7. The public title describes CSRF leading to stored XSS. A successful attack could let an attacker abuse a user’s browser interaction to change trusted site content or settings.

Executive priority

Treat this as a high-priority WordPress plugin exposure if the plugin is present. It is not confirmed as actively exploited in the provided sources, but stored XSS risk on public sites can affect trust, users, and incident response workload.

Technical view

The CVE describes a network-reachable CSRF issue with low attack complexity and required user interaction. Patchstack’s title frames the impact as stored XSS. The CVSS 3.1 score is 7.1 with changed scope and low confidentiality, integrity, and availability impact. Public source data does not name a fixed version.

Likely exposure

Exposure is most likely on WordPress sites running the Varnish WordPress plugin varnish-wp at version 1.7 or earlier. The provided affected metadata is sparse, so organizations should verify actual plugin presence and version rather than relying only on asset catalogs.

Exploitation context

The bundle does not show CISA KEV inclusion or any cited evidence of active exploitation. The CVSS vector requires user interaction, which fits CSRF-style abuse. Patchstack’s title indicates stored XSS impact, but the supplied CVE description only explicitly names CSRF.

Researcher notes

Source evidence is limited. The title says CSRF to stored XSS, while the CVE description centers on CSRF. No exploit details, fixed version, or mitigation is included in the bundle. Validate against vendor and Patchstack records before making assertions beyond version <=1.7 exposure.

Mitigation direction

  • Inventory WordPress sites for the varnish-wp plugin and installed version.
  • Check AdminGeekZ, WordPress plugin, and Patchstack guidance for a fixed release.
  • Update the plugin if a vendor-supported fixed version is available.
  • Disable or remove the plugin where it is not operationally required.
  • Limit WordPress admin exposure and reinforce administrator phishing protections.

Validation and detection

  • Confirm whether any WordPress site runs varnish-wp version 1.7 or earlier.
  • Review plugin advisories for fixed-version or workaround details before remediation.
  • Check recent WordPress admin changes affecting Varnish plugin settings or stored content.
  • Inspect affected sites for unexpected stored scripts or altered plugin configuration.
  • Document uncertainty where installed version or vendor fix status cannot be confirmed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-31616 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-31616Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdminGeekZVarnish WordPressvarnish-wp, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.