CVE-2024-1476
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 · uneditedThe Under Construction / Maintenance Mode from Acurax plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.6 via the REST API. This makes it possible for unauthenticated attackers to obtain the contents of posts and pages when maintenance mode is active thus bypassing 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 · moderate confidenceThe Acurax Under Construction / Maintenance Mode plugin for WordPress has a vulnerability in all versions up to 2.6 where the REST API endpoints remain publicly accessible even when maintenance mode is active. This allows unauthenticated attackers to bypass the maintenance mode protection and retrieve the full contents of posts and pages via REST API calls, exposing sensitive information that should be hidden.
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<= 2.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Acurax plugin is installedCheck WordPress plugins directory or admin panel for 'Acurax Under Construction / Maintenance Mode' pluginAffected if Plugin is not installed on the WordPress site
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate the Acurax plugin to view its version number, or check the plugin's main PHP file for the Version header commentAffected if Version is 2.6 or lower
-
Confirm maintenance mode is enabledAccess the plugin settings in WordPress admin under the Acurax plugin menu and verify if 'Enable Maintenance Mode' or similar option is turned onAffected if Maintenance mode is currently active on the site
-
Test REST API accessibility during maintenance modeWith the site showing maintenance mode, attempt a REST API request such as GET /wp-json/wp/v2/posts or GET /wp-json/wp/v2/pages using a tool like curl or browser developer tools while NOT logged inAffected if REST API returns full post/page content (200 OK with data) instead of being blocked or returning maintenance page
A site is affected if it has Acurax Under Construction / Maintenance Mode plugin version 2.6 or lower with maintenance mode enabled, and the REST API remains accessible to unauthenticated users exposing content that should be hidden.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the Acurax plugin to a version beyond 2.6 which should contain the fix for properly restricting REST API access during maintenance mode. If no patched version is available, consider alternative maintenance mode solutions or manually restrict REST API endpoints via server configuration.
latest available version on wordpress.org (after 2.6)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'Under Construction / Maintenance Mode' plugin by Acurax
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
- 6. After updating, verify that maintenance mode still functions correctly and that the REST API no longer exposes content to unauthenticated users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-1476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1476 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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