LiveActive security incident?Get immediate response
CVE Record

CVE-2024-1476: Under Construction / Maintenance Mode from Acurax <= 2.6 - Information Exposure

The 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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can let outsiders read WordPress posts and pages that the Acurax maintenance-mode plugin was meant to hide. The business risk is premature disclosure of unpublished, staged, or sensitive site content while maintenance mode is active.

Executive priority

Treat this as a medium-priority confidentiality issue. It is unlikely to cause system takeover, but it can expose private launch, maintenance, or staging content to unauthenticated visitors.

Technical view

CVE-2024-1476 is an information exposure issue in Under Construction / Maintenance Mode from Acurax for WordPress, reported for versions up to and including 2.6. Unauthenticated REST API access can bypass the plugin's maintenance-mode protection and expose post or page contents. CVSS is 5.3, CWE-284.

Likely exposure

Exposure is most likely on public WordPress sites using this plugin at version 2.6 or earlier, especially when maintenance mode is active and site content is assumed hidden.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates network access, low complexity, no privileges, and no user interaction, with limited confidentiality impact.

Researcher notes

Evidence is limited to the CVE description, Wordfence reference, and WordPress plugin listing. The provided data does not name a fixed version or confirmed exploitation. Validate exposure defensively and avoid assuming all hidden WordPress content is protected by this plugin.

Mitigation direction

  • Inventory WordPress sites for the Acurax maintenance-mode plugin and installed version.
  • Check vendor, WordPress.org, and Wordfence guidance for a fixed version or removal advice.
  • Do not rely on maintenance mode to protect confidential pages or posts.
  • Remove or restrict sensitive content from affected sites until exposure is resolved.
  • Disable or replace the plugin if no vendor-supported fix is available.

Validation and detection

  • Identify sites running Under Construction / Maintenance Mode from Acurax version 2.6 or earlier.
  • Confirm whether maintenance mode is active on each affected site.
  • Review unauthenticated REST API behavior for unintended post or page visibility.
  • Check access logs for unusual unauthenticated REST API requests during maintenance windows.
  • Document affected URLs and content sensitivity for remediation prioritization.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-1476 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2024-1476Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
acuraxUnder Construction / Maintenance Mode from Acurax0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.