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

CVE-2025-58677

HIGH · 7.1 CVSS v3.1 Published 2025-09-22
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 puravida1976 ShrinkTheWeb (STW) Website Previews shrinktheweb-website-preview-plugin allows Stored XSS.This issue affects ShrinkTheWeb (STW) Website Previews: from n/a through <= 2.8.5.

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

A CSRF vulnerability in the ShrinkTheWeb Website Preview WordPress plugin (version <= 2.8.5) allows attackers to trick authenticated administrators into submitting malicious requests that result in stored XSS payloads being persisted in the database. When other users view the affected pages, the injected JavaScript executes in their browsers.

MitigationUpdate the plugin to the latest version if a patch is available; otherwise, implement nonces/tokens on all state-changing operations and validate request origins to prevent CSRF exploitation leading to stored XSS.

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 plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ShrinkTheWeb Website Preview' or check the /wp-content/plugins/ directory for a folder named similar to 'stw' or 'shrinktheweb'.
    Affected if The plugin is present in the WordPress installation.
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin to view its details, or inspect the main plugin PHP file header for 'Version:' tag.
    Affected if The installed version is 2.8.5 or lower.
  3. Confirm plugin is active
    In Plugins > Installed Plugins, verify the plugin status shows 'Active' under the plugin name.
    Affected if The plugin is active.
  4. Inspect database for stored XSS
    Query the WordPress options table (wp_options) for suspicious JavaScript tags or encoded payloads in any option_name values that may be related to the plugin settings (look for option_names containing 'stw', 'shrink', or 'preview').
    Affected if Unexpected script tags, iframe tags, or event handlers (onload, onerror, onclick) are found stored in plugin-related options.
  5. Review pages for injected scripts
    Visit pages on the site where the plugin preview feature is used and view the page source to check for unexpected script tags, or use browser developer tools to inspect DOM for injected JavaScript.
    Affected if Unexpected JavaScript executes in the browser or script tags appear in the rendered HTML that were not intentionally added.

A user is affected if the ShrinkTheWeb Website Preview plugin (version 2.8.5 or lower) is installed and active, or if suspicious script payloads are found stored in the database related to the plugin.

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

Update the plugin to the latest version if a patch is available; otherwise, implement nonces/tokens on all state-changing operations and validate request origins to prevent CSRF exploitation leading to stored XSS.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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