Saphali Woocommerce Lite stored cross-site scripting in WordPress plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.3
- Who is exposed
- Specific setups only
Summary
Saphali Woocommerce Lite, a WordPress plugin from Saphali, has a stored cross-site scripting flaw in versions up to and including 2.0.2. An attacker can reach it remotely without logging in, but a user has to take an action for the malicious script to run.
Written by a model
Original description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Saphali Saphali Woocommerce Lite saphali-woocommerce-lite allows Stored XSS.This issue affects Saphali Woocommerce Lite: from n/a through 2.0.2.
Who should check
Teams running the Saphali Woocommerce Lite WordPress plugin, version 2.0.2 or earlier, on their WordPress sites
“Plugin <= 2.0.2 is vulnerable”
What to do
Check whether your setup matches what the bug needs.
Saphali Woocommerce Lite plugin version 2.0.2 or earlierUpgrade to a fixed version: 2.0.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128999 (WordPress Saphali Woocommerce Lite plugin <= 2.0.2 - Cross Site Scripting (XSS) vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128999 (entry last updated 2026-11-19):
Affected:
- Saphali Saphali Woocommerce Lite: fixed in 2.0.3
Fixed versions: 2.0.3.
Conditions (all must be true for the bug to be hit):
- Saphali Woocommerce Lite plugin version 2.0.2 or earlier (source: https://patchstack.com/database/wordpress/plugin/saphali-woocommerce-lite/vulnerability/wordpress-saphali-woocommerce-lite-plugin-2-0-2-cross-site-scripting-xss-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-128999 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128999 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/saphali-woocommerce-lite/vulnerability/wordpress-saphali-woocommerce-lite-plugin-2-0-2-cross-site-scripting-xss-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128999
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128999"}.Affected versions
- saphali-woocommerce-litefixed in 2.0.3 · through 2.0.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128999 |
| Record | NVD · CVE-2026-128999 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/saphali-woocommerce-lite/vulnerability/wordpress-saphali-woocommerce-lite-plugin-2-0-2-cross-site-scripting-xss-vulnerability?_s_id=cve |
Questions about CVE-2026-128999
Is CVE-2026-128999 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The plugin fails to properly sanitize input, so an attacker can inject malicious scripts into pages of the site. Those scripts can steal visitor data or hijack user accounts.
Source: patchstack.com
Which versions are affected by CVE-2026-128999?
saphali-woocommerce-lite: through 2.0.2 (fixed in 2.0.3).
Source: cve.now feed data
Am I affected, and how do I check?
Saphali Woocommerce Lite plugin version 2.0.2 and earlier are affected. To check, look at the plugin version listed on the WordPress Plugins screen or in the plugin's header.
Source: patchstack.com
How do I fix CVE-2026-128999?
Update the Saphali Woocommerce Lite plugin to version 2.0.3 or later, which is the fixed version named by the advisory.
Source: patchstack.com
Related
- CVE-2023-25788WordPress Saphali Woocommerce Lite Plugin <= 1.8.13 is vulnerable to Cross Site Request Forgery (CSRF)
- CVE-2025-12643Saphali LiqPay for donate <= 1.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
- CVE-2026-22308Missing authentication for critical function leading to reflected cross-site scripting in JTL-Shop
- CVE-2026-22309Stored cross-site scripting in JTL-Shop
- CVE-2026-130158RepoManager: Stored XSS via host-reported package metadata
- CVE-2026-131260Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.