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

CVE-2026-32460

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themefic Ultimate Addons for Contact Form 7 ultimate-addons-for-contact-form-7 allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Ultimate Addons for Contact Form 7: from n/a through <= 3.5.36.

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 · moderate confidence

Stored Cross-site Scripting (XSS) vulnerability in Themefic Ultimate Addons for Contact Form 7 plugin allows injection of malicious scripts through improperly sanitized input that gets rendered in web pages. The description indicates the vulnerability is related to incorrectly configured access control security levels, suggesting the XSS may be exploitable due to insufficient authorization checks.

MitigationUpdate to the latest patched version of Ultimate Addons for Contact Form 7. If no patch is available, implement output encoding and input validation at the application level or deploy a WAF rule to block XSS payloads until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ultimate Addons for Contact Form 7' by Themefic, or check the plugins directory for the presence of the /ultimate-addons-for-contact-form-7/ folder
    Affected if The plugin is installed and active
  2. Identify installed version
    In WordPress admin > Plugins, click on the plugin name to view details, or check the main plugin PHP file header for 'Version:' or query the WordPress options table for the plugin version option
    Affected if The installed version matches the affected version range (if known) or is an unpatched version
  3. Check for admin user privilege
    Verify if the WordPress installation has users with administrator or editor roles who can access the plugin settings, as the XSS may require elevated privileges to inject payloads
    Affected if The site has admin/editor users who have access to plugin configuration areas where input sanitization is lacking
  4. Inspect stored data for XSS payloads
    Check WordPress postmeta, options tables, or any custom tables created by the plugin for suspicious script tags (<script>, <img onerror=, javascript:, etc.)
    Affected if Malicious script tags are found stored in the database related to the plugin's fields
  5. Review plugin form configurations
    Access the plugin's form builder or settings area in WP Admin and examine any text input fields, particularly those that accept custom HTML or allow rich text input, for unsanitized stored values
    Affected if Custom input fields in the plugin's forms contain unescaped HTML or JavaScript that could execute in a browser
  6. Check browser console for XSS warnings
    Visit pages that render plugin-generated content and open browser developer tools to look for blocked XSS warnings or script execution errors
    Affected if XSS is being triggered or blocked when viewing plugin-generated pages

A user is affected if they have the Themefic Ultimate Addons for Contact Form 7 plugin installed with an unpatched version and the plugin's input fields are accessible to users with sufficient privileges to inject malicious scripts that get stored and rendered without proper sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of Ultimate Addons for Contact Form 7. If no patch is available, implement output encoding and input validation at the application level or deploy a WAF rule to block XSS payloads until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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