dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-56071

HIGH · 7.1 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Unauthenticated Cross Site Scripting (XSS) in Forminator <= 1.53.1 versions.

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

Unauthenticated Cross Site Scripting (XSS) vulnerability in Forminator plugin versions 1.53.1 and below allows attackers to inject malicious JavaScript through form submissions without requiring authentication. The injected payload executes when administrators or other users view the submitted data in the WordPress dashboard.

MitigationUpdate Forminator to version 1.53.2 or later to patch the XSS vulnerability. If immediate update is not possible, consider disabling the plugin or restricting form access until the patch can be applied.

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

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Verify Forminator plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Forminator and note the version number, or check the main plugin file header via FTP at wp-content/plugins/forminator/forminator.php
    Affected if Version is 1.53.1 or below (any version from 1.0 up to and including 1.53.1)
  2. Confirm active Forminator forms exist
    Go to Forminator > Forms in the WordPress dashboard and identify any published forms
    Affected if One or more forms are published and active on the site
  3. Verify unauthenticated form submissions are enabled
    Edit each active form and check the form settings under 'Permissions' or 'Availability' to see if 'Anyone can submit' or a similar public access setting is enabled
    Affected if Forms allow submissions without authentication (default Forminator behavior)
  4. Examine form submissions for XSS payloads
    Go to Forminator > Submissions and review submitted data fields for suspicious content such as <script> tags, javascript: URLs, or HTML event handlers like onload/onerror/onclick
    Affected if Any submitted data contains script tags, JavaScript URIs, or HTML event attributes

The environment is affected if Forminator version 1.53.1 or below is installed AND at least one form allows unauthenticated submissions, regardless of whether malicious payloads are currently visible in submissions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Forminator to version 1.53.2 or later to patch the XSS vulnerability. If immediate update is not possible, consider disabling the plugin or restricting form access until the patch can be applied.

Recommended fix Moderate confidence

Forminator latest version (newer than 1.53.1)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find Forminator plugin
  4. Check if current version is 1.53.1 or below
  5. If vulnerable, click 'Update Now' to install the latest available version
  6. Alternatively, download the latest Forminator plugin from the official WordPress repository and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version is newer than 1.53.1

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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