Contact FormWordPress extension · Supsystic
CVE-2023-45068
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Supsystic Contact Form by Supsystic plugin <= 1.7.27 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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the Supsystic Contact Form by Supsystic WordPress plugin affecting versions 1.7.27 and prior. The vulnerability allows attackers to induce authenticated users to perform unintended state-changing actions (such as modifying form configurations or submitting forms on their behalf) by tricking them into visiting malicious pages. CSRF attacks exploit the trust a web application places in authenticated users' 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
Contact FormWordPress extension
<= 1.7.27CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify Supsystic Contact Form plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Supsystic Contact Form' or 'Contact Form by Supsystic' in the listAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the Plugins list, click on the plugin name or view details to see the version number. Compare against 1.7.27Affected if The installed version is 1.7.27 or lower
-
Confirm the plugin is activeIn Plugins > Installed Plugins, verify the plugin shows as 'Active' rather than 'Inactive'Affected if The plugin is currently active on the WordPress site
-
Inspect form handling for nonce validationAccess the plugin files via FTP or File Manager, locate PHP files handling form submissions (typically in the main plugin directory or includes folder), and search for 'wp_nonce_field', 'wp_nonce', 'verify_nonce', or 'check_admin_referer' in form processing codeAffected if No nonce verification functions are found in the form submission handlers
A user is affected if the Supsystic Contact Form plugin is installed, active, and running version 1.7.27 or lower without proper CSRF token validation in its form handling code.
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 Supsystic Contact Form plugin to the latest version which should include proper anti-CSRF token (nonce) validation for all state-changing operations. If no patched version is available, implement nonce verification on all form submissions and AJAX handlers within the plugin as a temporary workaround.
Fix this in Contact Form
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45068 — 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-45068 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