What is the CVSS score of CVE-2026-57668?

CVE-2026-57668 has a CVSS 3.1 base score of 7.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L. EPSS exploitation probability: 0.3%.

Which versions of NEX-Forms are affected by CVE-2026-57668?

Basix NEX-Forms plugin (versions ≤9.2.2) contains a stored cross-site scripting vulnerability with no public exploit identified at time of analysis, creating persistent injection points in WordPress…

How to fix or mitigate CVE-2026-57668?

Within 24 hours, audit all WordPress installations for Basix NEX-Forms deployment and current version (vulnerable if ≤9.2.2); immediately disable the plugin if operationally feasible or restrict WordPress administrator access to trusted networks via IP allowlist. Over the next 7 days, monitor Patchstack and vendor channels for patch availability; test any released patch in a staging environment before production deployment; if no patch emerges, evaluate alternative form-builder plugins (WPForms, Gravity Forms, Formidable Forms) and begin migration planning. Within 30 days, deploy either a vendor patch (if released) or complete migration to a non-vulnerable alternative, ensuring no Basix NEX-Forms versions ≤9.2.2 remain in production.

NEX-Forms CVE-2026-57668

EUVD-2026-43353 HIGH

Cross-site Scripting (XSS) (CWE-79)

2026-07-13 Patchstack

WordPress XSS Nex Forms Wordpress Plugin

7.1

CVSS 3.1 · Vendor: Patchstack

Severity by source

Vendor (Patchstack) PRIMARY

7.1 HIGH

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

vuln.today AI

6.5 MEDIUM

Stored XSS in a form plugin typically needs some contributor/submission access (PR:L) and a victim rendering the payload (UI:R); scope changes (S:C) with low C/I/A confined to the browser context.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:L/SI:L/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

Analysis Generated

Jul 13, 2026 - 10:53 vuln.today

CVE Published

Jul 13, 2026 - 08:41 cve.org

HIGH 7.1

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Basix NEX-Forms nex-forms-express-wp-form-builder allows Stored XSS.This issue affects NEX-Forms: from n/a through <= 9.2.2.

AnalysisAI

Stored cross-site scripting in Basix NEX-Forms (WordPress form-builder plugin) affects all versions up to and including 9.2.2, letting an attacker persist malicious script that executes in a victim's browser when they view the affected form or its stored data. Reported by Patchstack and scored CVSS 7.1 with a scope change, the flaw can lead to session/credential theft or admin actions within the WordPress origin. No public exploit is identified at time of analysis and it is not on CISA KEV.

Technical ContextAI

NEX-Forms (cpe:2.3:a:basix:nex-forms:*) is a drag-and-drop form-builder plugin for WordPress used to create forms and collect submissions. The root cause is CWE-79, Improper Neutralization of Input During Web Page Generation: user-controllable input is stored (in form fields, settings, or submission records) and later rendered into an HTML page without proper output encoding or sanitization. Because the payload is persisted server-side and re-served, this is Stored (Type-2) XSS rather than reflected, so the script fires whenever a subsequent user renders the tainted content - typically inside the WordPress admin/editor or a public form page.

RemediationAI

Upgrade NEX-Forms to a release later than 9.2.2 once the vendor publishes a fixed build; consult the Patchstack advisory (https://patchstack.com/database/Wordpress/Plugin/nex-forms-express-wp-form-builder/vulnerability/wordpress-nex-forms-plugin-9-2-2-cross-site-scripting-xss-vulnerability) for the exact patched version, which is not stated in the available data - No vendor-released patch version identified at time of analysis. Until a fixed version is confirmed, restrict who can create or edit forms and who can submit form content to trusted users only, review existing forms and stored submissions for injected script, and place a WAF or virtual patch (Patchstack/Wordfence) in front of the site to filter XSS payloads; note that tightening form-submission access can break workflows relying on anonymous public submissions, so validate against your use case. Enforcing strong admin authentication and reviewing admin activity reduces the impact of a fired payload.