NextmoveWordPress extension · Xlplugins
CVE-2025-62969
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in XLPlugins NextMove Lite woo-thank-you-page-nextmove-lite allows Stored XSS.This issue affects NextMove Lite: from n/a through <= 2.23.0.
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 confidenceStored XSS vulnerability in XLPlugins NextMove Lite (woo-thank-you-page-nextmove-lite) plugin allows attackers to inject malicious JavaScript code through unsanitized input fields on the thank-you page. This payload gets persisted in the database and executes whenever users view the affected page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
NextmoveWordPress extension
<= 2.23.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify NextMove Lite plugin is installedCheck your WordPress installation under wp-content/plugins/ for the folder 'woo-thank-you-page-nextmove-lite', or view installed plugins in wp-admin > PluginsAffected if The plugin folder 'woo-thank-you-page-nextmove-lite' exists in the plugins directory
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'NextMove Lite - Custom Thank You Page For WooCommerce'. The version number is displayed below the plugin name. Alternatively, check the 'woo-thank-you-page-nextmove-lite/readme.txt' file for the 'Version:' fieldAffected if The installed version is 2.23.0 or lower (any version up to and including 2.23.0)
-
Confirm thank-you page is activeIn WordPress admin, navigate to NextMove Lite settings (usually under WooCommerce > NextMove Lite or a dedicated menu item). Check if a thank-you page has been created and enabledAffected if A thank-you page is created and enabled in the NextMove Lite settings (the vulnerability only affects the thank-you page functionality)
-
Inspect stored data for suspicious scriptsAccess your WordPress database (via phpMyAdmin or command line). Look in the wp_posts table for posts with post_type 'nm_thankyou' or similar custom post type used by NextMove. Inspect the post_content field for unencoded script tags, javascript: URIs, or onload/onerror event handlersAffected if The database contains posts with post_type related to NextMove that contain raw <script> tags, javascript: protocols, or event handlers like onload, onerror, or onclick in the content fields
You are affected if the NextMove Lite plugin version is 2.23.0 or lower AND a thank-you page is enabled, particularly if the database contains unsanitized script content in the thank-you page post records.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade NextMove Lite to version 2.24.0 or later which contains the security patch. As a temporary measure, disable the plugin until the update can be applied.
Fix this in Nextmove
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62969 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62969 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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