CVE-2025-52735
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 Reflected XSS.This issue affects NextMove Lite: from n/a through <= 2.24.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 confidenceA reflected Cross-site Scripting (XSS) vulnerability exists in the NextMove Lite WordPress plugin (woo-thank-you-page-nextmove-lite) versions through 2.24.0. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that gets reflected in the web page generation process.
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<= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify NextMove Lite plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'NextMove Lite' or 'woo-thank-you-page-nextmove-lite'. Alternatively, check the wp-content/plugins directory for a folder named 'woo-thank-you-page-nextmove-lite'.Affected if The plugin folder exists in the WordPress installation
-
Determine installed plugin versionIn WordPress admin Plugins list, click on the plugin to view details and read the version number. Or open the main plugin file (e.g., woo-thank-you-page-nextmove-lite.php) and look for the 'Version' field in the plugin header comment.Affected if The version number is 2.23.0 or lower
-
Confirm the plugin handles user-supplied input in thank you pagesReview the plugin settings in WordPress admin under the NextMove Lite menu. Check if the plugin displays order data, customer inputs, or custom fields on the order received/thank you page.Affected if The plugin is configured to display any user-tangible data on the checkout thank you page
-
Inspect for unsanitized reflected parametersSubmit a test order and examine the resulting thank you page URL and HTML source. Look for any URL parameters (such as order ID, custom fields, or query strings) that appear reflected in the page content without encoding.Affected if Any URL parameters from user input are reflected verbatim in the thank you page HTML without proper encoding
If the NextMove Lite plugin version is 2.23.0 or lower and the plugin displays any user-supplied or order-related data on the thank you page, the environment is likely affected by this reflected XSS vulnerability.
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 dataUpdate NextMove Lite to the latest version available from XLPlugins, which should contain proper input sanitization/encoding. If no update is available, implement output encoding for all user-supplied parameters before rendering in HTML.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52735 — 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-52735 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