Ultimate Addons For Contact Form 7WordPress extension · Themefic
CVE-2023-30493
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Themefic Ultimate Addons for Contact Form 7 plugin <= 3.2.0 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 confidenceAn unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the Themefic Ultimate Addons for Contact Form 7 plugin for WordPress in versions 3.2.0 and below. The vulnerability allows remote attackers to inject arbitrary JavaScript code through vulnerable parameters that are reflected in the application's response without proper sanitization or output encoding.
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
< 3.2.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedNavigate to WordPress admin > Plugins and locate 'Themefic Ultimate Addons for Contact Form 7' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the Plugins list, click on the plugin to view its details, or check the plugin header in /wp-content/plugins/ultimate-addons-for-contact-form-7/Affected if The displayed version is 3.2.0 or lower (any version below 3.2.1)
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the plugin status shows as 'Active'Affected if The plugin is currently active and serving pages to visitors
-
Confirm unauthenticated exposureThis plugin exposes functionality to unauthenticated users by default; no special configuration required. Ensure the plugin is not restricting access via firewall or access control.Affected if The plugin is active and accessible to unauthenticated visitors (default state)
If the plugin is installed, active, and its version is 3.2.0 or below, the environment is affected by this reflected XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.2.1
Update the Themefic Ultimate Addons for Contact Form 7 plugin to a version newer than 3.2.0, or disable the plugin until an official patch can be applied.
3.2.1
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Themefic Ultimate Addons for Contact Form 7'
- Click 'Update now' or 'Update' to update the plugin to version 3.2.1 or later
- Verify the update was successful by checking the plugin version
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
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30493 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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