dbcve.org
Forminator FormsWordPress extension · Wpmudev

CVE-2025-0469

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-27
Fix available
A fix is available. Upgrade to 1.39.3 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 Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the slider template data in all versions up to, and including, 1.39.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, 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 Forminator WordPress plugin versions up to 1.39.2 fail to properly sanitize and escape the slider template data field, allowing authenticated users with Contributor-level access to inject malicious JavaScript. This stored XSS executes whenever users access pages containing the injected slider template.

MitigationUpgrade the Forminator plugin to version 1.39.3 or later, which includes proper input sanitization and output escaping for slider template data. Alternatively, restrict Contributor-level user permissions until the patch is applied.

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
Forminator FormsWordPress extension
Affected:< 1.39.3

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. Check Forminator plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate Forminator, and verify the version number displayed
    Affected if Version is lower than 1.39.3 (e.g., 1.39.2, 1.39.1, etc.)
  2. Confirm Forminator plugin is active
    In the Plugins list, verify that Forminator shows as 'Active' under the plugin status
    Affected if Plugin is active and version is below 1.39.3
  3. Identify Contributor-level users
    Go to Users > All Users in WordPress admin and check the role column for any users with Contributor role
    Affected if Contributor users exist and have access to create or edit Forminator content
  4. Inspect slider templates for injected scripts
    Navigate to Forminator > Templates (or Custom Form > Slider) in the admin panel and examine any saved slider template data fields for suspicious script tags or event handlers
    Affected if Slider templates contain unsanitized JavaScript code such as <script> tags or javascript: URIs in data fields

You are affected if Forminator plugin version is below 1.39.3, the plugin is active, and slider templates containing malicious script injection exist in your environment.

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 1.39.3 or later
Fixed in 1.39.3
Interim mitigation

Upgrade the Forminator plugin to version 1.39.3 or later, which includes proper input sanitization and output escaping for slider template data. Alternatively, restrict Contributor-level user permissions until the patch is applied.

Recommended fix High confidence

1.39.3

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Find the Forminator Forms plugin
  4. Click Update Now to install version 1.39.3 or later
  5. Verify the update was successful by checking the plugin version

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

Fix this in Forminator Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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