dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1181

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 Coming Soon, Under Construction & Maintenance Mode By Dazzler plugin for WordPress is vulnerable to maintenance mode bypass in all versions up to, and including, 2.1.2. This is due to the plugin relying on the REQUEST_URI to determine if the page being accesses is an admin area. This makes it possible for unauthenticated attackers to bypass maintenance mode and access the site which may be considered confidential when in maintenance mode.

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 Dazzler Coming Soon plugin for WordPress versions up to 2.1.2 uses the REQUEST_URI server variable to determine if a user is accessing the admin area, in order to allow admin access while blocking public access during maintenance mode. This method is trivially bypassed because REQUEST_URI can be manipulated by attackers, allowing unauthenticated visitors to bypass maintenance mode protections and view site content intended to be hidden.

MitigationUpdate the plugin to version 2.1.3 or later which properly uses WordPress built-in functions like is_admin() to determine admin context, or if no update is available, disable the plugin and implement alternative maintenance mode via server-level controls (.htaccess or nginx configuration).

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 Dazzler Coming Soon plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Dazzler Coming Soon' or check the wp-content/plugins directory for a folder named 'dazzler-coming-soon' or similar
    Affected if Plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, click on the plugin in the plugins list to view version details, or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if Version is 2.1.2 or lower (any version up to and including 2.1.2)
  3. Verify if maintenance mode is currently enabled
    Access the plugin settings page in WordPress admin (usually under Settings > Coming Soon or a dedicated Dazzler menu) and check if the maintenance mode toggle is turned on or active
    Affected if Maintenance mode is enabled and the site is in maintenance state
  4. Check for the vulnerable REQUEST_URI pattern in plugin code
    Inspect the main plugin PHP file (typically index.php or main class file in the plugin folder) and search for code using $_SERVER['REQUEST_URI'] to determine admin access context, particularly in conditional statements controlling maintenance mode bypass
    Affected if Code uses REQUEST_URI for admin access checks and allows public access when this check is bypassed

A user is affected if the Dazzler Coming Soon plugin version 2.1.2 or lower is installed, maintenance mode is enabled, and the plugin relies on REQUEST_URI for admin access determination rather than WordPress is_admin() function.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.1.3 or later which properly uses WordPress built-in functions like is_admin() to determine admin context, or if no update is available, disable the plugin and implement alternative maintenance mode via server-level controls (.htaccess or nginx configuration).

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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