dbcve.org
Coming Soon \& Maintenance ModeWordPress extension · Colorlib

CVE-2024-1473

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-20
Fix available
A fix is available. Upgrade to after 1.0.99 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 by Colorlib plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.0.99 via the REST API. This makes it possible for unauthenticated attackers to obtain post and page contents via REST API thus bypassing maintenance mode protection provided by the plugin.

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 by Colorlib WordPress plugin fails to properly protect its REST API endpoints. Unauthenticated attackers can bypass the maintenance mode display and retrieve the full contents of posts and pages through the REST API, exposing sensitive site content despite the plugin's intended protection.

MitigationUpdate the plugin to version 1.1.0 or later, which adds proper authentication checks to REST API endpoints to enforce maintenance mode protection. If immediate update is not possible, consider disabling the REST API or implementing additional access controls at the server level.

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 Soon \& Maintenance ModeWordPress extension
Affected:<= 1.0.99

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 the plugin is installed
    Check your WordPress installation under wp-content/plugins/ for the folder 'colorlib-coming-soon-maintenance' or view the installed plugins in WordPress admin panel
    Affected if The plugin folder exists in the plugins directory regardless of version
  2. Identify the installed plugin version
    Look in the plugin's main PHP file (usually index.php or main plugin file) for the version comment header, or check in WordPress admin under Plugins > Installed Plugins
    Affected if The version is 1.0.99 or lower, or if no version number is displayed (indicating an old installation)
  3. Confirm maintenance mode is enabled
    Check the plugin settings in WordPress admin under the plugin's settings page, or inspect the site frontend to see if the Coming Soon/Maintenance page is being displayed to visitors
    Affected if The maintenance mode is turned ON and visitors see a Coming Soon or Maintenance page
  4. Test unauthenticated REST API access
    Send a GET request to your site /wp-json/wp/v2/posts (or other /wp-json/ endpoints) using curl or a browser while NOT logged in, for example: curl -s https://yoursite.com/wp-json/wp/v2/posts
    Affected if The API returns full post content (title, body, etc.) without requiring any authentication, which means the plugin is not properly protecting the REST API
  5. Check for sensitive content exposure
    Review the JSON response from the REST API call - look for full post/page content in the 'content' or 'excerpt' fields rather than just summaries or restricted content
    Affected if Full post/page content is visible in the API response, exposing content that should be protected by maintenance mode

You are affected if the Colorlib Coming Soon & Maintenance Mode plugin version is 1.0.99 or lower AND maintenance mode is enabled AND the REST API returns full content without authentication.

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

Update the plugin to version 1.1.0 or later, which adds proper authentication checks to REST API endpoints to enforce maintenance mode protection. If immediate update is not possible, consider disabling the REST API or implementing additional access controls at the server level.

Recommended fix Moderate confidence

1.0.100 or latest available version on wordpress.org

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Coming Soon & Maintenance Mode by Colorlib'
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/coming-soon-maintenance-mode and upload via Plugins > Add New > Upload Plugin
  5. Verify the updated version is 1.0.100 or higher
  6. Test that maintenance mode is functioning correctly and that unauthenticated users can no longer access content via REST API

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

Fix this in Coming Soon \& Maintenance Mode 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-2024-1473 — 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-2024-1473 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