Knit Pay stored XSS in generated pages
- Exploited
- No known exploitation
- Fix
- Fixed in 9.6.5.0
- Who is exposed
- Specific setups only
Summary
Knit Pay, a WordPress plugin, has a stored cross-site scripting flaw that lets an attacker plant malicious script in pages it generates. The attack can be carried out remotely without logging in, but it requires a user to take an action, such as opening a crafted page.
Written by a model
Original description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Knit Pay Knit Pay knit-pay allows Stored XSS.This issue affects Knit Pay: from n/a through 9.6.4.0.
Who should check
Sites running the WordPress Knit Pay plugin version 9.6.4.0 or earlier
“WordPress Knit Pay Plugin <= 9.6.4.0”
What to do
Check whether your setup matches what the bug needs.
Knit Pay WordPress plugin version 9.6.4.0 or earlierUpgrade to a fixed version: 9.6.5.0.
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-129007 (WordPress Knit Pay plugin <= 9.6.4.0 - 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-129007 (entry last updated 2026-11-20):
Affected:
- Knit Pay Knit Pay: fixed in 9.6.5.0
Fixed versions: 9.6.5.0.
Conditions (all must be true for the bug to be hit):
- Knit Pay WordPress plugin version 9.6.4.0 or earlier (source: https://patchstack.com/database/wordpress/plugin/knit-pay/vulnerability/wordpress-knit-pay-plugin-9-6-4-0-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-129007 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129007 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/knit-pay/vulnerability/wordpress-knit-pay-plugin-9-6-4-0-cross-site-scripting-xss-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-129007
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-129007
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-129007"}.Affected versions
- knit-payfixed in 9.6.5.0 · through 9.6.4.0
cve.now Index
- Exploitation0/40No signal
- 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
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129007 |
| Record | NVD · CVE-2026-129007 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/knit-pay/vulnerability/wordpress-knit-pay-plugin-9-6-4-0-cross-site-scripting-xss-vulnerability?_s_id=cve |
Questions about CVE-2026-129007
Is CVE-2026-129007 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 Knit Pay WordPress plugin does not properly handle some input, so an attacker can inject malicious scripts into pages of the site. Those scripts can steal visitor data or hijack visitor accounts.
Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-129007?
knit-pay: through 9.6.4.0 (fixed in 9.6.5.0).
Source: cve.now feed data
Am I affected, and how do I check?
Knit Pay WordPress plugin versions 9.6.4.0 and earlier are affected. To check a site, look at the installed Knit Pay plugin version in the WordPress Plugins screen or the plugin's header information.
Source: patchstack.com, cve.org
How do I fix CVE-2026-129007?
Update the Knit Pay WordPress plugin to version 9.6.5.0 or later, the first fixed version named in the advisory.
Source: patchstack.com, cve.org
Related
- CVE-2026-114191WordPress UPI QR Code Payment Gateway for WooCommerce plugin <= 1.6.3 - Broken Access Control vulnerability
- CVE-2026-49070WordPress Knit Pay plugin <= 9.4.0.0 - Broken Access Control vulnerability
- CVE-2026-112821WordPress Knit Pay plugin <= 9.6.3.0 - Broken Access Control vulnerability
- CVE-2026-56023WordPress UPI QR Code Payment Gateway for WooCommerce plugin <= 1.6.2 - Broken Access Control vulnerability
- CVE-2026-129053WordPress Knit Pay plugin <= 9.6.5.0 - Broken Access Control vulnerability
- CVE-2026-129009WordPress UPI QR Code Payment Gateway for WooCommerce plugin <= 1.7.0 - Broken Access Control vulnerability
No corrections so far. Something wrong on this page? Report an error.