dbcve.org
Quick Contact FormWordPress extension · Fullworksplugins

CVE-2023-23885

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-07
Fix available
A fix is available. Upgrade to after 8.0.3.1 or later.
See remediation →
58/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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Quick Contact Form plugin <= 8.0.3.1 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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in the Fullworks Quick Contact Form plugin allows authenticated users with contributor or higher privileges to inject malicious JavaScript through form inputs. The injected script is stored in the database and executes when other users (typically administrators) view the affected pages containing the contact form submissions.

MitigationUpdate the Fullworks Quick Contact Form plugin to a version newer than 8.0.3.1. Until an update is available, restrict contributor-level user capabilities or disable the plugin.

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
Quick Contact FormWordPress extension
Affected:<= 8.0.3.1

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
None

CVSS:3.1/AV:N/AC:L/PR:L/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 installation and version
    Navigate to WordPress admin dashboard > Plugins. Locate 'Fullworks Quick Contact Form' or 'Quick Contact Form' by Fullworksplugins. Check the version number displayed in the plugin details. Alternatively, inspect the plugin header in /wp-content/plugins/quick-contact-form/quick-contact-form.php or check the version in the plugin's main PHP file.
    Affected if The plugin is installed and the version is 8.0.3.1 or lower.
  2. Check for stored XSS in form submissions
    Access the WordPress database (via phpMyAdmin or command line). Query the plugin's form submission table (commonly named similar to wp_quick_contact_form_submissions or similar, check _options table for table names). Look for suspicious patterns in submission fields such as <script, javascript:, onload=, onerror=, or encoded HTML entities that may contain XSS payloads.
    Affected if Form submission records contain unsanitized HTML or JavaScript code, particularly in fields that should only accept plain text.
  3. Review contributor-level user accounts
    In WordPress admin, go to Users > All Users. Identify any users with the 'Contributor' role. Check the user list for unexpected or suspicious usernames that may indicate a compromised account. Also review Users > Profile for any added malicious capabilities.
    Affected if There are contributor-level users present, especially ones that are unknown or unexpected, as they could have injected the malicious content.
  4. Inspect browser execution of stored scripts
    If form submission data is displayed in the WordPress admin area (e.g., in the plugin's submissions view page), navigate to that page with a browser's developer console open (F12). Look for any script execution or console errors that indicate injected JavaScript is running.
    Affected if JavaScript executes automatically when viewing the plugin's submissions or contact form data in the admin panel.

If the Fullworks Quick Contact Form plugin version is 8.0.3.1 or lower AND there are stored XSS payloads in the database or unexpected contributor users, the environment is affected by this vulnerability.

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 8.0.3.1
Interim mitigation

Update the Fullworks Quick Contact Form plugin to a version newer than 8.0.3.1. Until an update is available, restrict contributor-level user capabilities or disable the plugin.

Recommended fix High confidence

Version 8.0.4 or later (any version above 8.0.3.1)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'Quick Contact Form' by Fullworks plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, you can manually download the updated plugin version and reinstall

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

Fix this in Quick Contact Form 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-23885 — 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-23885 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