dbcve.org
Maintenance ModeWordPress extension · Helderk

CVE-2024-1478

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 3.0.2 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 Maintenance Mode plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.1 via the REST API. This makes it possible for unauthenticated attackers to obtain post and page content via API thus bypassing the content 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 Maintenance Mode WordPress plugin has a sensitive information exposure vulnerability in its REST API. The API endpoint that serves post and page content lacks proper authorization checks, allowing unauthenticated attackers to bypass the plugin's content protection mechanism and retrieve protected content via the REST API.

MitigationUpdate the Maintenance Mode plugin to version 3.0.2 or later to receive the patch. If immediate update is not possible, consider disabling the REST API endpoint or adding firewall rules to restrict access.

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
Maintenance ModeWordPress extension
Affected:< 3.0.2

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 Maintenance Mode plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Maintenance Mode' by Helderk, or check the plugin files in /wp-content/plugins/ directory
    Affected if The plugin is present in the installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Maintenance Mode and view the version number, or inspect the main plugin file header in /wp-content/plugins/hk-maintenance-mode/
    Affected if Version is below 3.0.2 (compare your version against the affected range)
  3. Confirm REST API endpoint is active
    Send a GET request to /wp-json/ and check if the maintenance mode endpoint is listed, or try accessing /wp-json/hk-maintenance-mode/v1/ (adjust path based on actual endpoint structure)
    Affected if REST API endpoints are accessible without authentication
  4. Test for unauthorized content access
    With maintenance mode active and content protection enabled, send an unauthenticated REST API request to retrieve post/page content (such as /wp-json/wp/v2/posts or /wp-json/wp/v2/pages)
    Affected if Protected content is returned via REST API while maintenance mode is active, indicating the authorization bypass is present

You are affected if the Maintenance Mode plugin is installed with a version below 3.0.2 and unauthenticated REST API requests can retrieve protected content while maintenance mode is active.

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

Update the Maintenance Mode plugin to version 3.0.2 or later to receive the patch. If immediate update is not possible, consider disabling the REST API endpoint or adding firewall rules to restrict access.

Recommended fix High confidence

Maintenance Mode plugin version 3.0.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Maintenance Mode' plugin in the list
  4. If an update is available, click 'Update Now' to update to version 3.0.2
  5. Alternatively, go to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/maintenance-mode
  6. After updating, verify the plugin version shows 3.0.2 under Plugins > Installed Plugins
  7. Test that the REST API no longer exposes protected content to unauthenticated users

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

Fix this in Maintenance Mode Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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