highCVE-2026-57708

Database for Contact Form 7, WPforms, Elementor forms <= 1.5.2 - Unauthenticated Stored Cross-Site Scripting

Database for Contact Form 7, WPforms, Elementor forms has a cross-site scripting issue. Unsafe script can run in another user's browser if the vulnerable feature is used.

ProductDatabase for Contact Form 7, WPforms, Elementor forms
CVSS7.1
EPSS0.0018
UpdatedJuly 15, 2026

Quick answer

Database for Contact Form 7, WPforms, Elementor forms should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • Database for Contact Form 7, WPforms, Elementor forms up to and including 1.5.2

Fixed versions

  • Database for Contact Form 7, WPforms, Elementor forms 1.5.3 or later

How to fix it

Update Database for Contact Form 7, WPforms, Elementor forms. The old version can let unsafe script run in a user or admin browser.

  1. Back up the site and database.
  2. Update Database for Contact Form 7, WPforms, Elementor forms to Database for Contact Form 7, WPforms, Elementor forms 1.5.3 or later.
  3. Clear all site and plugin caches.
  4. Review recent posts, settings, forms, and widgets for unknown script.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version is Database for Contact Form 7, WPforms, Elementor forms 1.5.3 or later.
  • Test the affected feature and confirm script input is blocked or cleaned.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-57708?

Database for Contact Form 7, WPforms, Elementor forms versions listed as affected should be reviewed: Database for Contact Form 7, WPforms, Elementor forms up to and including 1.5.2.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.