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

CVE-2026-13378

HIGH · 7.2 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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 Form Vibes – Database Manager for Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Contact Form 7 Form Field in all versions up to, and including, 1.5.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers 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 Form Vibes WordPress plugin fails to properly sanitize and escape data from Contact Form 7 form fields, allowing unauthenticated attackers to inject malicious JavaScript code that persists in the database. This stored XSS executes whenever users access pages containing the injected content.

MitigationUpgrade to version 1.5.3 or later which includes proper input sanitization and output escaping. Until then, consider disabling the plugin or implementing additional WAF rules.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Form Vibes plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Form Vibes' in the list
    Affected if The plugin is present in the WordPress installation
  2. Check installed Form Vibes version
    Click on the plugin name in Plugins list or check the plugin header in /wp-content/plugins/form-vibes/ folder to find the version number
    Affected if Version is lower than 1.5.3 (or version cannot be determined and plugin is present)
  3. Verify Contact Form 7 is active and integrated
    Check if Contact Form 7 plugin is active and if Form Vibes settings show integration with any CF7 forms
    Affected if CF7 is active and Form Vibes is configured to capture CF7 submissions (the plugin only affects CF7 data)
  4. Inspect stored form submissions in database
    Access the WordPress database (via phpMyAdmin or CLI) and query the formvibes_submissions table or any table prefixed with fv_ for suspicious script tags or HTML in stored form data
    Affected if Database contains entries with unescaped HTML/script tags in form fields submitted via Contact Form 7

User is affected if Form Vibes plugin is installed with version below 1.5.3 and Contact Form 7 integration is active, especially if the database shows injected script content in form submission records.

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

Upgrade to version 1.5.3 or later which includes proper input sanitization and output escaping. Until then, consider disabling the plugin or implementing additional WAF rules.

Recommended fix High confidence

Version 1.5.3 or later (latest available version from wordpress.org/plugins/form-vibes)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Form Vibes – Database Manager for Forms'
  4. Check the current installed version matches 1.5.2 or below
  5. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/form-vibes
  6. After updating, verify the new version is installed (should be version 1.5.3 or higher)
  7. Consider reviewing submitted form entries in the plugin to check for any malicious XSS payloads that may have been injected prior to patching and remove them

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

Have this fixed 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 help mitigating

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-2026-13378 — 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-13378 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