dbcve.org
Ultimate Addons For Contact Form 7WordPress extension · Themefic

CVE-2023-49766

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to after 3.2.0 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themefic Ultimate Addons for Contact Form 7 allows Stored XSS.This issue affects Ultimate Addons for Contact Form 7: from n/a through 3.2.0.

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

A stored cross-site scripting (XSS) vulnerability in Themefic Ultimate Addons for Contact Form 7 (versions through 3.2.0) allows attackers to inject malicious JavaScript payloads through contact form submissions. When WordPress administrators view these submissions in the admin dashboard, the stored payload executes, potentially allowing session hijacking or administrative actions.

MitigationUpdate to version 3.2.1 or later which contains the security fix. Audit existing form submissions in the WordPress admin for any malicious content and clean or remove compromised entries.

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
Ultimate Addons For Contact Form 7WordPress extension
Affected:<= 3.2.0

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Themefic Ultimate Addons for Contact Form 7'. Check the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/ultimate-addons-for-contact-form-7/ or via WP-CLI: wp plugin list --name='ultimate-addons-for-contact-form-7'
    Affected if The installed version is 3.2.0 or lower (any version through 3.2.0)
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the plugin shows as 'Active'. Attackers can only inject payloads through submissions if the plugin is actively processing forms.
    Affected if The plugin is active and the version is 3.2.0 or lower
  3. Inspect contact form submissions for malicious scripts
    In WordPress admin, navigate to the submissions section for your contact forms (typically under Contact > Submissions or within the form builder). Review recent entries for unusual characters, script tags, javascript: URLs, or encoded content that may contain XSS payloads.
    Affected if Any submission entries contain suspicious JavaScript code, event handlers, or script tags that could execute in an admin context
  4. Check browser console for executed XSS
    As a WordPress administrator, open your browser developer tools (F12) and navigate to the submissions viewing area in the admin panel. Check the Console tab for any JavaScript errors or warnings that may indicate executed malicious scripts.
    Affected if JavaScript errors or unexpected behavior occurs when viewing submissions in the admin dashboard

A user is affected if the Themefic Ultimate Addons for Contact Form 7 plugin version is 3.2.0 or lower AND the plugin is active AND the site has received form submissions that could contain malicious XSS payloads.

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 a release after 3.2.0
Interim mitigation

Update to version 3.2.1 or later which contains the security fix. Audit existing form submissions in the WordPress admin for any malicious content and clean or remove compromised entries.

Recommended fix Low confidence

Latest version of Ultimate Addons for Contact Form 7 (newer than 3.2.0)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Update Ultimate Addons for Contact Form 7 plugin to the latest available version from the WordPress plugin repository
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin > Plugins
  4. 4. Test the contact form functionality to ensure the plugin continues to work correctly after the update
Caveat Minor or major compatibility changes possible with Contact Form 7 or WordPress updates; test in staging environment first

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

Fix this in Ultimate Addons For Contact Form 7 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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