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

CVE-2026-1396

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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 Magic Conversation For Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'magic-conversation' shortcode in all versions up to, and including, 3.0.97 due to insufficient input sanitization and output escaping on user supplied attributes. 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 Magic Conversation For Gravity Forms WordPress plugin is vulnerable to stored XSS via the 'magic-conversation' shortcode in versions up to 3.0.97. Authenticated attackers with contributor-level access can inject arbitrary JavaScript through unsanitized shortcode attributes, which executes when other users view affected pages.

MitigationUpdate the plugin to version 3.0.98 or later which includes proper input sanitization and output escaping for shortcode attributes.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm plugin is installed
    Go to WordPress admin > Plugins and look for 'Magic Conversation For Gravity Forms' in the installed plugins list
    Affected if plugin is not present on the system
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the plugin details to view the installed version number, then compare against the fixed version 3.0.98
    Affected if installed version is lower than 3.0.98
  3. Identify shortcode usage
    Search the WordPress database or content for the '[magic-conversation]' shortcode by reviewing page/post content or using a search tool like: SELECT * FROM wp_posts WHERE post_content LIKE '%[magic-conversation]%'
    Affected if the shortcode is present in any published content and the plugin version is below 3.0.98
  4. Verify shortcode has user-supplied attributes
    Examine any pages/posts containing the shortcode and check if custom attributes are used (e.g., [magic-conversation id="123" custom_attr="value"]), as the vulnerability exploits unsanitized shortcode attributes
    Affected if shortcode with custom attributes is in use and version is below 3.0.98

A user is affected if the Magic Conversation For Gravity Forms plugin version is below 3.0.98 AND the magic-conversation shortcode with custom attributes appears in any published content, allowing stored XSS execution when visitors view those pages.

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 the plugin to version 3.0.98 or later which includes proper input sanitization and output escaping for shortcode attributes.

Recommended fix Moderate confidence

Version 3.0.98 or later of the Magic Conversation For Gravity Forms plugin

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Magic Conversation For Gravity Forms' plugin
  4. Check if an update is available for the plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  7. After updating, verify the plugin is running version 3.0.98 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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