dbcve.org
Nifty Coming Soon \& Maintenance Mode PageWordPress extension · Wpconcern

CVE-2020-36707

HIGH · 8.8 CVSS v3.1 Published 2023-06-07
Fix available
A fix is available. Upgrade to 1.58 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
The Coming Soon & Maintenance Mode Page plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.57. This is due to confusing logic functions missing or having incorrect nonce validation. This makes it possible for unauthenticated attackers to gain and perform otherwise unauthorized access and 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 confidence

The Coming Soon & Maintenance Mode Page WordPress plugin versions up to 1.57 are vulnerable to Cross-Site Request Forgery due to missing or incorrect nonce validation in form handling logic. This allows unauthenticated attackers to forge requests by tricking administrators into clicking malicious links, potentially leading to unauthorized configuration changes.

MitigationUpdate the plugin to version 1.58 or later which includes proper nonce validation. Until updated, avoid clicking untrusted links while logged into WordPress admin.

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
Nifty Coming Soon \& Maintenance Mode PageWordPress extension
Affected:< 1.58

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. Locate the plugin in WordPress
    Access your WordPress installation via FTP or file manager, navigate to /wp-content/plugins/ and check for a folder named 'nifty-coming-coming-soon' or similar variant containing 'nifty' and 'maintenance' in the name
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed version
    Open the main plugin PHP file (usually named nifty-coming-soon.php or similar) and locate the version comment in the file header, or check the plugin version listed in WordPress admin under Plugins > Installed Plugins
    Affected if The displayed version number is lower than 1.58 (for example: 1.57, 1.56, etc.)
  3. Confirm the plugin is active
    Log into WordPress admin panel, go to Plugins > Installed Plugins and verify whether the Nifty Coming Soon plugin shows as 'Active'
    Affected if The plugin status shows as Active
  4. Verify form handling is accessible
    Navigate to the plugin settings page in WordPress admin (usually under Settings or a dedicated menu item for the plugin) to confirm the form handling logic is present and accessible
    Affected if The plugin settings page loads and contains form submission options for configuration

Your environment is affected if the Nifty Coming Soon & Maintenance Mode Page plugin is installed, active, and the version is lower than 1.58, exposing the CSRF vulnerability in the form handling logic.

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 1.58 or later
Fixed in 1.58
Interim mitigation

Update the plugin to version 1.58 or later which includes proper nonce validation. Until updated, avoid clicking untrusted links while logged into WordPress admin.

Recommended fix High confidence

1.58

  1. 1. Create a complete backup of your WordPress site (database and files)
  2. 2. Navigate to the WordPress admin dashboard > Plugins
  3. 3. Locate the 'Nifty Coming Soon & Maintenance Mode Page' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.58 or later
  5. 5. Alternatively, manually upload version 1.58 or newer from the WordPress plugin repository
  6. 6. After updating, verify the plugin version in the installed plugins list confirms version 1.58 or higher is active
  7. 7. Test that the Coming Soon/Maintenance mode functionality works correctly

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

Fix this in Nifty Coming Soon \& Maintenance Mode Page Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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