Contact Form BuilderWordPress extension · Wpdevart
CVE-2023-46075
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 wpdevart Contact Form Builder, Contact Widget plugin <= 2.1.6 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 · moderate confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in wpdevart Contact Form Builder and Contact Widget plugin versions 2.1.6 and below. The vulnerability allows attackers to inject malicious scripts through unsanitized user inputs that are reflected back in the application's response.
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
Contact Form BuilderWordPress extension
<= 2.1.6CVSS 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 installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'wpdevart Contact Form Builder' or 'Contact Form Builder and Contact Widget' in the list. Alternatively, check for the plugin directory in wp-content/plugins/ for folders containing 'contact-form' and 'wpdevart'.Affected if The plugin is listed as active or installed in WordPress
-
Identify installed versionIn the WordPress Plugins page, click on the plugin name or view the plugin header file (typically main PHP file in the plugin directory) to find the 'Version' declared in the plugin metadata comment block.Affected if The version number displayed is 2.1.6 or lower
-
Identify plugin endpoint handling user inputExamine the plugin's PHP files for parameters received via GET or POST requests that are processed and reflected in output. Look for common input vectors like 'name', 'email', 'subject', 'message', or custom form field parameters in the plugin's frontend submission handling code.Affected if The plugin processes user-supplied parameters without sanitization before reflecting them in the response
-
Test for reflected XSS behaviorSubmit a crafted request to the plugin's form submission endpoint using a test parameter with a benign XSS payload such as '<script>alert(1)</script>' or '" onmouseover="alert(1)"' and observe if the payload is reflected unsanitized in the resulting page response.Affected if The submitted payload appears exactly in the page output without being escaped or encoded
A user is affected if the wpdevart Contact Form Builder plugin version 2.1.6 or lower is installed and active, and form submission parameters are reflected in the response without output encoding.
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.
From vendor dataUpdate the wpdevart Contact Form Builder plugin to a version newer than 2.1.6. If immediate update is not possible, implement output encoding and input validation on all user-supplied parameters.
Fix this in Contact Form Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46075 — 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-46075 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