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

CVE-2025-31570

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 wp-buy Related Posts Widget with Thumbnails advanced-css3-related-posts-widget allows Stored XSS.This issue affects Related Posts Widget with Thumbnails: from n/a through <= 1.2.

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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Related Posts Widget with Thumbnails plugin allows authenticated administrators to be tricked into submitting malicious requests that inject persistent JavaScript payloads (Stored XSS) into the widget's stored configuration. When other users view pages containing the affected widget, the injected script executes in their browsers.

MitigationUpdate to a patched version of the plugin once released; until then, disable the plugin or restrict admin access. The underlying fix requires implementing CSRF tokens/nonces on all admin form actions and ensuring proper output escaping.

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. Verify the Related Posts Widget with Thumbnails plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Related Posts Widget with Thumbnails' in the installed plugins list
    Affected if The plugin appears in the installed plugins list and is activated
  2. Determine the installed plugin version
    Click on the plugin in the Plugins list to view its details, or check the plugin's main PHP file header for the Version comment
    Affected if The installed version matches any version known to be affected by CVE-2025-31570 (compare against published advisory once available)
  3. Inspect admin configuration forms for CSRF protection
    Access the plugin settings page (usually under Settings or Appearance > Related Posts), view the HTML source of any forms, and check if each form includes a nonce field (wpnonce) or CSRF token
    Affected if Forms lack nonce/CSRF token fields in the HTML source
  4. Test for Stored XSS in widget configuration
    Submit a test payload in plugin settings (such as a text field with <script>alert('test')</script>), save the settings, then view the page source to verify if the input is properly escaped or raw
    Affected if The submitted payload executes as JavaScript when viewing a page with the widget, indicating lack of output escaping

You are affected if the plugin is installed and active, its version falls within the affected range (once known), and admin forms lack CSRF tokens or fail to escape stored configuration values.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the plugin once released; until then, disable the plugin or restrict admin access. The underlying fix requires implementing CSRF tokens/nonces on all admin form actions and ensuring proper output escaping.

Recommended fix Moderate confidence

Update to the latest version of Related Posts Widget with Thumbnails (advanced-css3-related-posts-widget) available in the WordPress plugin repository

  1. 1. Log into the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Related Posts Widget with Thumbnails' (advanced-css3-related-posts-widget)
  4. 4. Check the current installed version is 1.2 or lower
  5. 5. If an update is available, click 'Update Now' to install the patched version
  6. 6. Verify the update completed successfully
  7. 7. Test the related posts functionality to ensure normal operation

Generated from the published advisory — verify against the referenced sources before acting.

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