dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-1477

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-20
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 Easy Maintenance Mode plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.2 via the REST API. This makes it possible for authenticated attackers to obtain post and page content via REST API thus bypassign the 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 Easy Maintenance Mode WordPress plugin fails to properly restrict REST API access when maintenance mode is active. Authenticated attackers (with any user role) can query the REST API to retrieve post and page content that should be hidden during maintenance mode, effectively bypassing the plugin's core protective function.

MitigationUpdate the Easy Maintenance Mode plugin to a version beyond 1.4.2. If no patched version is available, consider alternative maintenance mode solutions or implement additional server-level access controls on REST API endpoints.

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. Identify if Easy Maintenance Mode plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Easy Maintenance Mode' in the installed plugins list, or check the /wp-content/plugins/ directory for the easy-maintenance-mode folder
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the Easy Maintenance Mode plugin to view its version number, or read the main plugin PHP file header for the Version field
    Affected if The version is 1.4.2 or lower (versions beyond 1.4.2 contain the fix)
  3. Verify if maintenance mode is currently active
    Check the plugin settings in WordPress admin under Easy Maintenance Mode, or inspect the site frontend to see if a maintenance notice is displayed
    Affected if Maintenance mode is enabled and the plugin is active
  4. Test REST API endpoint access while maintenance mode is active
    Use a web browser or curl to request https://your-site.com/wp-json/wp/v2/posts and https://your-site.com/wp-json/wp/v2/pages while maintenance mode is enabled; include a low-privilege user authentication token or no authentication
    Affected if The API returns post/page content that should be hidden during maintenance mode (HTTP 200 with data instead of expected 403 or maintenance notice)
  5. Confirm authenticated user role access
    Log in with a subscriber or other minimal-role user account and attempt to access the REST API endpoints while maintenance mode is active
    Affected if Any authenticated user role can retrieve content via REST API that should be concealed during maintenance mode

A user is affected if Easy Maintenance Mode version 1.4.2 or lower is installed, maintenance mode is enabled, and the REST API returns hidden content to authenticated users of any role.

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 Easy Maintenance Mode plugin to a version beyond 1.4.2. If no patched version is available, consider alternative maintenance mode solutions or implement additional server-level access controls on REST API endpoints.

Recommended fix Moderate confidence

Easy Maintenance Mode version 1.4.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Easy Maintenance Mode plugin
  4. If an update is available, click 'Update Now'
  5. Alternatively, navigate to Dashboard > Updates and update the plugin from there
  6. After updating, verify the plugin is running version 1.4.3 or later

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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