dbcve.org
Coming SoonWordPress extension · Supsystic

CVE-2023-22714

HIGH · 8.8 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to after 1.7.10 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Supsystic Coming Soon by Supsystic plugin <= 1.7.10 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Supsystic Coming Soon WordPress plugin versions 1.7.10 and below allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.

MitigationUpdate the Supsystic Coming Soon plugin to the latest version immediately. If no update is available, consider disabling the plugin until a patched version is released.

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
Coming SoonWordPress extension
Affected:<= 1.7.10

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Supsystic Coming Soon plugin is installed
    Navigate to the WordPress plugins directory (wp-content/plugins/) and look for a folder named 'coming-soon' or search for files containing 'supsystic'
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically found in the plugin root directory) and locate the 'Version' header in the plugin comment block at the top of the file
    Affected if The version read from the file is 1.7.10 or lower
  3. Verify plugin status in WordPress admin
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins to confirm whether the Coming Soon plugin is active
    Affected if The plugin appears in the installed plugins list and is activated
  4. Confirm version falls within affected range
    Compare the identified version number against the CVE-affected range: any version <= 1.7.10 is vulnerable
    Affected if Installed version is 1.7.10 or any version number lower than 1.7.10

You are affected if the Supsystic Coming Soon plugin is installed and running version 1.7.10 or below.

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.

From vendor data
Upgrade available Upgrade to a release after 1.7.10
Interim mitigation

Update the Supsystic Coming Soon plugin to the latest version immediately. If no update is available, consider disabling the plugin until a patched version is released.

Fix this in Coming Soon Scoped from the published advisory
  • Consultation1.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22714 — 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-22714 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