Wcp Contact FormWordPress extension · Webcodin
CVE-2023-22703
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 Webcodin WCP Contact Form plugin <= 3.1.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 confidenceUnauthenticated reflected Cross-Site Scripting (XSS) vulnerability in Webcodin WCP Contact Form plugin versions 3.1.0 and below. Attackers can inject malicious JavaScript through unsanitized input parameters in the contact form, which gets reflected back in the server response and executed in victim browsers.
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
Wcp Contact FormWordPress extension
<= 3.1.0CVSS 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 Webcodin WCP Contact Form plugin is installedList installed WordPress plugins via admin dashboard under Plugins > Installed Plugins, or run: wp plugin list --status=active --format=csvAffected if Webcodin Wcp Contact Form appears in the active plugins list
-
Identify installed plugin versionNavigate to Plugins > Installed Plugins and locate the plugin, or inspect the main plugin file header in wp-content/plugins/wcp-contact-form/ for 'Version:' tag, or run: grep -r 'Version:' wp-content/plugins/wcp-contact-form/Affected if Version displayed is 3.1.0 or lower, or the version field is missing/unreadable (older versions may lack proper version headers)
-
Locate the contact form submission endpointAccess the site frontend and locate any published contact form using this plugin, then check the HTML form action attribute for the submission URL (commonly /?wcp_contact_form=submit or similar), or review plugin source files for form handling codeAffected if The plugin publishes a contact form that accepts user input without requiring authentication
-
Test for reflected XSS in form parametersSubmit a test request with a harmless XSS probe in common form fields (name, email, subject, message) such as <script>alert(1)</script> or <img src=x onerror=alert(1)>, then inspect the server response to see if the payload is returned unsanitizedAffected if The submitted payload appears verbatim in the response without HTML encoding (e.g., <script> tags execute or appear in page source)
If the Webcodin WCP Contact Form plugin version 3.1.0 or below is installed and a contact form is publicly accessible, the environment is vulnerable to reflected XSS via unsanitized form inputs.
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 Webcodin WCP Contact Form plugin to the latest version to patch the vulnerability. As a temporary workaround, implement proper input validation and output encoding on user-supplied data.
Fix this in Wcp Contact Form
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22703 — 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-22703 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