dbcve.org
Nex FormsWordPress extension · Basixonline

CVE-2025-4208

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

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 Limited Code Execution in all versions up to, and including, 8.9.1 via the get_table_records function. This is due to the unsanitized use of user-supplied input in call_user_func(). This makes it possible for authenticated attackers, with Custom-level access, to execute arbitrary PHP functions that meet specific constraints (static methods or global functions accepting a single array parameter).

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 up to version 8.9.1 contains a limited code execution vulnerability in the get_table_records function. The function uses call_user_func() with unsanitized user-supplied input, allowing authenticated attackers with Custom-level access to invoke arbitrary static methods or global functions that accept a single array parameter.

MitigationUpgrade to version 8.9.2 or later. Until then, restrict the Custom-level role permissions and monitor for suspicious calls to the get_table_records function.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Check NEX-Forms plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Nex Forms, or inspect the plugin main file header for the 'Version' field
    Affected if The installed version is 8.9.2 or earlier (versions prior to the fix)
  2. Verify Custom-level role presence
    In WordPress admin, go to Users > Roles or inspect wp_options table for role capabilities; the Custom role is a default role created by NEX-Forms
    Affected if A Custom role exists with elevated permissions (this role is created by NEX-Forms and grants form management access)
  3. Inspect get_table_records function code
    Locate the plugin PHP files (typically in wp-content/plugins/nex-forms) and search for the get_table_records function; examine if call_user_func() uses unsanitized $_POST or $_REQUEST input
    Affected if The function contains call_user_func() using raw user input without sanitization (e.g., call_user_func($_REQUEST['action']) or similar)
  4. Monitor for suspicious function calls in logs
    Review web server access logs (Apache/nginx) and WordPress debug logs for requests to admin-ajax.php or admin-post.php containing get_table_records with unusual action parameters
    Affected if Logs show requests invoking the get_table_records endpoint with unexpected function/method names as parameters

You are affected if NEX-Forms version 8.9.2 or earlier is installed and any user possesses the Custom-level role, combined with evidence of unsafe call_user_func usage in the get_table_records function or suspicious calls to that endpoint in your logs.

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 a release after 8.9.2
Interim mitigation

Upgrade to version 8.9.2 or later. Until then, restrict the Custom-level role permissions and monitor for suspicious calls to the get_table_records function.

Recommended fix Moderate confidence

NEX-Forms plugin version 8.9.3 or latest available

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'NEX-Forms – Ultimate Form Builder' plugin.
  4. 4. Check the current installed version displayed under the plugin name.
  5. 5. If the installed version is 8.9.2 or lower, click 'Update Now' to install the latest available version.
  6. 6. After the update completes, verify the new version number to confirm the patch was applied.
  7. 7. Ensure the site passes a security scan to verify the vulnerability is remediated.

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4208 — 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-4208 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