dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-1418

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 CGC Maintenance Mode plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.2 via the REST API. This makes it possible for unauthenticated attackers to view protected posts via REST API even when maintenance mode is enabled.

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 CGC Maintenance Mode WordPress plugin fails to properly restrict REST API access when maintenance mode is enabled. Unauthenticated attackers can exploit the REST API endpoint to bypass the maintenance mode protection and view protected posts that should be hidden.

MitigationUpdate the plugin to the latest patched version once available, or implement server-side access controls on the REST API endpoints to enforce authentication requirements regardless of maintenance mode settings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 CGC Maintenance Mode plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CGC Maintenance Mode'. Note the installed version number from the plugin details.
    Affected if Plugin is installed and version cannot be confirmed as patched against CVE-2024-1418 or is unknown
  2. Confirm maintenance mode is enabled
    Check the plugin settings in WordPress admin under the plugin's settings page, or inspect the database options table for the maintenance mode active configuration setting.
    Affected if Maintenance mode is turned ON and the plugin is installed
  3. Test REST API access during maintenance mode
    With maintenance mode active, send an unauthenticated GET request to the WordPress REST API endpoint (for example, /wp-json/wp/v2/posts or /wp-json/wp/v2/pages). Observe whether the API returns data without requiring authentication.
    Affected if The REST API returns HTTP 200 with post/page data without any authentication credentials while maintenance mode is enabled
  4. Verify protected posts are exposed via REST API
    Attempt to retrieve specific posts that are marked as private, draft, or otherwise hidden during maintenance mode via the REST API endpoint /wp-json/wp/v2/posts/{id} without authentication.
    Affected if Posts that should be hidden during maintenance mode are accessible via unauthenticated REST API calls

A user is affected if the CGC Maintenance Mode plugin is installed with maintenance mode enabled, and the REST API responds to unauthenticated requests exposing content that should be protected.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest patched version once available, or implement server-side access controls on the REST API endpoints to enforce authentication requirements regardless of maintenance mode settings.

Recommended fix Moderate confidence

Version 1.3 or later (confirm via WordPress plugin repository)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the CGC Maintenance Mode plugin
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, update to version 1.3 or later
  6. 6. Verify the fix by testing that protected posts are no longer accessible via REST API when maintenance mode is enabled

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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