CVE-2026-57668
Deferred Deferred - Pending Action

Stored XSS in NEX-Forms WordPress Plugin

Vulnerability report for CVE-2026-57668, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Patchstack

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-08-02
AI Q&A
2026-07-13
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
basix nex-forms to 9.2.2 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Stored Cross-site Scripting (XSS) issue in Basix NEX-Forms nex-forms-express-wp-form-builder. It occurs due to improper neutralization of input during web page generation, which means that malicious scripts can be injected and stored by the application, then executed in the context of users who view the affected pages.

Detection Guidance

Detecting this stored Cross-Site Scripting (XSS) vulnerability in NEX-Forms (versions through 9.2.2) on your system or network requires checking for vulnerable plugin installations and monitoring for suspicious input handling.

  • Check if the NEX-Forms plugin is installed on your WordPress site. You can do this by navigating to the WordPress admin dashboard, then to 'Plugins' and searching for 'NEX-Forms' or 'nex-forms-express-wp-form-builder'.
  • Verify the installed version of NEX-Forms. If it is version 9.2.2 or earlier, your system is vulnerable. This can be checked in the WordPress admin dashboard under 'Plugins'.
  • Inspect form submissions and stored data in the WordPress database for suspicious or malformed input. Use database queries to search for scripts or unusual content in form submission records. For example, you can use SQL queries like: SELECT * FROM wp_nex_forms_submissions WHERE form_data LIKE '%<script>%';
  • Monitor web traffic and logs for unusual activity, such as unexpected script execution or unauthorized form submissions. Tools like web application firewalls (WAFs) or log analyzers can help detect anomalous behavior.

Since this is a stored XSS vulnerability, manual testing may also be required. This involves submitting test payloads (e.g., <script>alert(1)</script>) into forms and checking if they are stored and rendered in the web application.

Impact Analysis

The vulnerability can allow attackers to execute arbitrary scripts in the browsers of users who visit the affected web pages. This can lead to unauthorized actions such as stealing user credentials, hijacking user sessions, defacing websites, or distributing malware.

Compliance Impact

This vulnerability, a Stored Cross-Site Scripting (XSS) issue, can impact compliance with standards and regulations like GDPR and HIPAA due to its potential to compromise data confidentiality, integrity, and availability.

  • GDPR: Stored XSS can lead to unauthorized access to sensitive user data or session hijacking, violating GDPR's requirements for data protection and privacy (e.g., Article 5 on data integrity and confidentiality, Article 32 on security of processing).
  • HIPAA: If the affected system processes protected health information (PHI), this vulnerability could expose PHI to unauthorized parties, violating HIPAA's Security Rule (e.g., 45 CFR Part 164, Subpart C) which mandates safeguards for electronic PHI.
  • Other standards: The vulnerability may also conflict with requirements in frameworks like PCI DSS (if payment data is involved) or ISO 27001, which emphasize secure coding practices and protection against injection attacks.

The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) indicates the vulnerability is exploitable remotely with low attack complexity, posing a moderate risk to compliance if not mitigated.

Mitigation Strategies

To mitigate this vulnerability, follow these immediate steps:

  • Update the NEX-Forms plugin to the latest version if a patch is available. Since the vulnerability affects versions through 9.2.2, check the plugin developer's website or the WordPress plugin repository for updates.
  • If no patch is available, consider disabling or removing the NEX-Forms plugin until a fix is released. This will prevent exploitation of the vulnerability.
  • Implement a web application firewall (WAF) to block malicious input and filter out XSS payloads. This can provide temporary protection while awaiting a patch.
  • Review and sanitize all form submissions and stored data in the WordPress database. Remove any suspicious or unauthorized scripts that may have been injected.
  • Monitor your website for unusual activity, such as unauthorized form submissions or unexpected script execution. Logs should be reviewed regularly to detect potential exploitation attempts.
  • Educate users and administrators about the risks of XSS vulnerabilities and the importance of input validation and output encoding.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57668. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart