Skip to main content
VulnerabilityPublished Updated

CVE-2026-15602: NEX-Forms (WordPress plugin) · SQL Injection

Affects NEX-Forms (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.9 Medium.

Data as of 13 Nov 2026, 23:53 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
webawaysNEX-Forms – Ultimate Forms Plugin for WordPressAffected
  • <=9.2.4
Fixed in–

AI-suggested

Until an official fix is available, restrict access to the plugin's administrative functions to trusted users only and monitor for suspicious activity related to CSV exports. Consider disabling or restricting the submission_report2 AJAX handler if possible. Avoid lowering capability requirements for this handler to subscriber level or less.

Description

The NEX-Forms – Ultimate Forms Plugin for WordPress plugin for WordPress is vulnerable to generic SQL Injection via the 'additional_params' parameter in all versions up to, and including, 9.2.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with admin-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is a second-order vulnerability; the payload is stored via the submission_report2 AJAX handler (which lacks a nonce check and relies solely on a capability that can be configured down to subscriber-level) and triggered when a CSV export is generated.

References

Community reviews

Loading reviews…