Imran CubeWP Forms DOM-based cross-site scripting in form handling
Affects the CubeWP Forms WordPress plugin, versions 1.1.12 and earlier. Fixed in 1.1.13.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.1.13
- Who is exposed
- Specific setups only
Summary
The CubeWP Forms plugin by Imran Tauqeer has a DOM-based cross-site scripting flaw that lets an attacker run malicious scripts in a user's browser. An attacker can reach it remotely without logging in, but a user must take an action before the attack works.
Written by a model
Original description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Imran Tauqeer CubeWP Forms cubewp-forms allows DOM-Based XSS.This issue affects CubeWP Forms: from n/a through 1.1.12.
Who should check
Teams running the CubeWP Forms WordPress plugin version 1.1.12 or earlier on their WordPress sites.
“<= 1.1.12 Vulnerable version(s)”
What to do
Check whether your setup matches what the bug needs.
CubeWP Forms plugin version 1.1.12 or earlierUpgrade to a fixed version: 1.1.13.
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-131797 (WordPress CubeWP Forms plugin <= 1.1.12 - 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-131797 (entry last updated 2026-11-20):
Affected:
- Imran Tauqeer CubeWP Forms: fixed in 1.1.13
Fixed versions: 1.1.13.
Conditions (all must be true for the bug to be hit):
- CubeWP Forms plugin version 1.1.12 or earlier (source: https://patchstack.com/database/wordpress/plugin/cubewp-forms/vulnerability/wordpress-cubewp-forms-plugin-1-1-12-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-131797 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131797 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/cubewp-forms/vulnerability/wordpress-cubewp-forms-plugin-1-1-12-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-131797
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-131797"}.Affected versions
- cubewp-formsfixed in 1.1.13 · through 1.1.12
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 2
| Kind | Source |
|---|---|
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131797 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/cubewp-forms/vulnerability/wordpress-cubewp-forms-plugin-1-1-12-cross-site-scripting-xss-vulnerability?_s_id=cve |
Questions about CVE-2026-131797
Is CVE-2026-131797 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?
This cross-site scripting flaw lets attackers inject malicious scripts into the site. The advisory says these scripts can steal visitor data or hijack visitors' accounts.
Source: patchstack.com
Which versions are affected by CVE-2026-131797?
cubewp-forms: through 1.1.12 (fixed in 1.1.13).
Source: cve.now feed data
Am I affected, and how do I check?
The advisory covers CubeWP Forms plugin version 1.1.12 or earlier. To check a site, look at the installed plugin version on the WordPress Plugins screen.
Source: patchstack.com
How do I fix CVE-2026-131797?
Update CubeWP Forms to version 1.1.13 or later, which is the listed fix.
Source: patchstack.com
Related
- CVE-2026-129075WordPress CubeWP Forms plugin <= 1.1.12 - Cross Site Scripting (XSS) vulnerability
- CVE-2024-47300WordPress CubeWP Forms plugin <= 1.1.1 - Cross Site Scripting (XSS) vulnerability
- CVE-2024-51651WordPress CubeWP Forms plugin <= 1.1.10 - Broken Access Control vulnerability
- CVE-2025-49880WordPress CubeWP Forms plugin <= 1.1.5 - Broken Access Control Vulnerability
- CVE-2025-54735WordPress CubeWP Framework Plugin <= 1.1.24 - Privilege Escalation Vulnerability
- CVE-2026-28168WordPress CubeWP plugin <= 1.1.30 - SQL Injection vulnerability
No corrections so far. Something wrong on this page? Report an error.