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

CVE-2025-28922

HIGH · 7.1 CVSS v3.1 Published 2025-03-11
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 Terence D. Go To Top go-to-top allows Stored XSS.This issue affects Go To Top: from n/a through <= 0.0.8.

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

The Go To Top WordPress plugin (versions <= 0.0.8) contains a CSRF vulnerability that allows attackers to craft malicious requests which, when triggered by an authenticated administrator, can inject and store XSS payloads into the plugin's settings or output. This combines two medium-severity issues (CSRF + Stored XSS) into a high-impact attack vector.

MitigationAdd nonce token verification to all form submissions and state-changing actions in the plugin to prevent CSRF, and implement proper input sanitization and output escaping to prevent stored XSS. Until a patched version is available, restrict admin access and monitor for suspicious 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
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. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > find 'Go To Top' and read the version number. Alternatively, check the main plugin file (usually /wp-content/plugins/go-to-top/目录下) for the 'Version' header in the plugin comment block.
    Affected if Version listed is 0.0.8 or lower
  2. Verify admin authentication status
    Review active WordPress admin sessions via Users > All Users in the dashboard, or check for any recently logged-in administrator accounts. Since this CSRF requires an authenticated administrator to trigger the attack, confirm whether any admin sessions exist.
    Affected if An authenticated administrator session exists and the plugin is active
  3. Inspect plugin settings in database for stored XSS
    Query the wp_options table (or equivalent) for rows where option_name contains 'goto' or the plugin's settings identifier. Look for any suspicious JavaScript tags, event handlers, or encoded payloads in option_value fields related to this plugin.
    Affected if Any plugin setting values contain script tags, javascript: URIs, or obvious XSS payloads
  4. Review plugin form submissions for missing nonce protection
    Examine the plugin's PHP source files in /wp-content/plugins/go-to-top/. Search for form handling code (POST/GET requests) and check if wp_nonce_field() or check_admin_referer() functions are present around state-changing actions.
    Affected if Form processing code exists without nonce verification calls (wp_nonce_field, check_admin_referer, or wp_verify_nonce)
  5. Check plugin output for unescaped settings rendering
    Examine plugin PHP files for any instances of settings values being output via echo or print without esc_html(), esc_attr(), or similar WordPress escaping functions.
    Affected if Plugin outputs setting values directly to HTML without proper escaping functions

A user is affected if the Go To Top plugin version is 0.0.8 or lower AND an authenticated administrator has accessed the site (allowing CSRF-triggered XSS injection) OR if malicious scripts are already stored in the plugin's 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

Add nonce token verification to all form submissions and state-changing actions in the plugin to prevent CSRF, and implement proper input sanitization and output escaping to prevent stored XSS. Until a patched version is available, restrict admin access and monitor for suspicious 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-28922 — 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-28922 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