dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-0703

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The NextMove Lite – Thank You Page for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'xlwcty_current_date' shortcode in all versions up to, and including, 2.23.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 NextMove Lite WordPress plugin fails to properly sanitize and escape user-supplied attributes in the xlwcty_current_date shortcode, allowing authenticated attackers with contributor-level access or higher to inject malicious JavaScript that persists on affected pages and executes when viewed by other users.

MitigationUpdate the plugin to a version newer than 2.23.0; if no update is available, implement proper input sanitization using sanitize_text_field() and output escaping using esc_attr() or esc_html() on the shortcode attributes.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

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 NextMove Lite plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'NextMove Lite' in the list
    Affected if The plugin is not found in the installed plugins list
  2. Check installed plugin version
    Click 'View details' on the NextMove Lite plugin in the Plugins page to display the installed version number
    Affected if The installed version is 2.23.0 or lower (the vulnerability is fixed in versions newer than 2.23.0)
  3. Identify usage of the vulnerable shortcode
    Search post content, page content, or widget areas for the shortcode [xlwcty_current_date]
    Affected if The [xlwcty_current_date] shortcode is present in any published content
  4. Check for contributor-level or higher user accounts
    In WordPress admin, go to Users and review user roles; contributor, author, editor, and administrator roles all have the privilege level required to exploit this flaw
    Affected if Any user account with contributor, author, editor, or administrator role exists on the site
  5. Inspect shortcode attributes in database
    Query the wp_posts table for posts containing 'xlwcty_current_date' and examine the post_content field for any attributes passed to the shortcode (e.g., format, class, style)
    Affected if The shortcode is used with custom attributes that could contain unsanitized user input

You are affected if the NextMove Lite plugin version is 2.23.0 or lower AND the [xlwcty_current_date] shortcode is in use on your site with users who have contributor-level or higher access.

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 the plugin to a version newer than 2.23.0; if no update is available, implement proper input sanitization using sanitize_text_field() and output escaping using esc_attr() or esc_html() on the shortcode attributes.

Recommended fix High confidence

2.23.1 or later

  1. Update the NextMove Lite – Thank You Page for WooCommerce plugin to the latest available version from the WordPress plugin repository
  2. After updating, verify that the xlwcty_current_date shortcode functions correctly on your thank you pages
  3. Confirm that contributor-level users can no longer inject arbitrary scripts through shortcode attributes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

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