Contact FormWordPress extension · Supsystic
CVE-2023-2528
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 · uneditedThe Contact Form by Supsystic plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.7.24. This is due to missing or incorrect nonce validation on the AJAX action handler. This makes it possible for unauthenticated attackers to execute AJAX actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe Contact Form by Supsystic WordPress plugin versions up to 1.7.24 lacks proper nonce validation on its AJAX action handlers. This allows unauthenticated attackers to forge requests that execute privileged AJAX actions by tricking administrators into clicking malicious links, potentially leading to configuration changes or data manipulation.
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.24CVSS 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.
-
Locate the Supsystic Contact Form plugin installationCheck your WordPress installation's /wp-content/plugins/ directory for a folder named 'contact-form-by-supsystic' or 'contact-form-supsystic', or view the installed plugins list in the WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the plugins directory
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find the Contact Form by Supsystic entry; the version number is displayed below the plugin name. Alternatively, check the main plugin PHP file (usually in the plugin folder) for a 'Version:' header in the file comment, or inspect the readme.txt file for the 'Stable tag' valueAffected if The displayed version is 1.7.24 or any version number lower than 1.7.24
-
Verify the AJAX action handler vulnerability existsExamine the main plugin PHP file and locate AJAX handler functions (functions hooked to 'wp_ajax_' or 'wp_ajax_nopriv_' actions). Look for AJAX callback functions that process requests without calling wp_verify_nonce() or check_admin_referer() to validate noncesAffected if AJAX handlers are found that do not contain nonce validation checks (wp_verify_nonce or check_admin_referer) before processing requests
You are affected if the Contact Form by Supsystic plugin is installed and its version is 1.7.24 or lower, as this version lacks proper nonce validation on AJAX action handlers.
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 plugin to the latest version which includes proper nonce validation for AJAX endpoints, or manually add wp_verify_nonce() checks to all AJAX action handlers in the plugin code.
Fix this in Contact Form
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2528 — 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-2528 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