dbcve.org
Nex FormsWordPress extension · Basixonline

CVE-2025-3468

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-08
Fix available
A fix is available. Upgrade to 8.9.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The NEX-Forms – Ultimate Form Builder – Contact forms and much more plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the clean_html and form_fields parameters in all versions up to, and including, 8.9.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Custom-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The NEX-Forms WordPress plugin fails to properly sanitize the clean_html and form_fields parameters, allowing authenticated users with Custom-level access to inject malicious JavaScript. Because the plugin does not escape output correctly, the injected scripts are stored and execute when other users access pages containing the affected form fields.

MitigationUpdate to version 8.9.2 or later where the vulnerability is patched. Until then, limit Custom-level user permissions and consider disabling the affected form functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nex FormsWordPress extension
Affected:< 8.9.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify NEX-Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'NEX-Forms' or 'Basixonline Nex Forms', or check the wp-content/plugins directory for a nex-forms folder
    Affected if The NEX-Forms plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin Plugins page, click on the plugin to view details and note the version number, or check the main plugin file header for the Version field
    Affected if The version number is less than 8.9.2
  3. Identify users with Custom-level access
    In WordPress admin, go to Users > All Users and review user roles. Custom-level access refers to users with a custom role or permission level that can access the NEX-Forms form builder feature
    Affected if Any user account exists with permissions sufficient to access the NEX-Forms form builder or form editing capabilities
  4. Confirm form creation capability is accessible
    In WordPress admin, check if a NEX-Forms menu item exists in the sidebar, indicating the plugin is active and its form building features are accessible to certain users
    Affected if The NEX-Forms admin menu is visible and users with Custom-level access can create or edit forms using the clean_html or form_fields parameters

You are affected if NEX-Forms plugin is installed with a version below 8.9.2 AND users with Custom-level access can access the form builder functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.9.2 or later
Fixed in 8.9.2
Interim mitigation

Update to version 8.9.2 or later where the vulnerability is patched. Until then, limit Custom-level user permissions and consider disabling the affected form functionality.

Recommended fix High confidence

8.9.2

  1. 1. Backup your WordPress site before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'NEX-Forms – Ultimate Form Builder' in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 8.9.2 or later.
  6. 6. Alternatively, download version 8.9.2 or later from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin version shows 8.9.2 or higher in the Plugins list.
  8. 8. Test that forms still function correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nex Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3468 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3468 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data