dbcve.org
Under Construction \/ Maintenance ModeWordPress extension · Acurax

CVE-2023-6922

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-28
Fix available
A fix is available. Upgrade to after 2.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Under Construction / Maintenance Mode from Acurax plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.6 via the 'acx_csma_subscribe_ajax' function. This can allow authenticated attackers to extract sensitive data such as names and email addresses of subscribed visitors.

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 acx_csma_subscribe_ajax function in the Acurax Under Construction/Maint Mode plugin for WordPress (versions up to 2.6) lacks proper authorization checks, allowing authenticated attackers to query and extract sensitive subscriber PII including names and email addresses via direct AJAX calls.

MitigationUpdate the plugin to version 2.7 or later which contains the security fix; alternatively, implement proper capability checks and nonce verification on the AJAX endpoint to restrict data access to authorized administrators only.

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
Under Construction \/ Maintenance ModeWordPress extension
Affected:<= 2.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Acurax plugin installation
    Check for the plugin directory 'acurax-under-construction' in wp-content/plugins/ or list installed plugins via WordPress admin or wp-cli: wp plugin list --status=active
    Affected if The plugin directory exists and the plugin appears in the WordPress plugin list as active
  2. Check installed plugin version
    Review the plugin main file header (e.g., acx-construction.php) for the 'Version' tag, or run: wp plugin list --filter=name=acurax-under-construction --format=json
    Affected if The version is 2.6 or lower, or if the version cannot be determined and the plugin is present
  3. Identify the vulnerable AJAX endpoint
    Inspect the plugin PHP files for the 'acx_csma_subscribe_ajax' function and its registration via add_action('wp_ajax_acx_csma_subscribe_ajax', ...) or check if wp-content/plugins/acurax-under-construction/ contains AJAX handler files
    Affected if The function exists and is hooked to a public AJAX action without capability checks (wp_ajax_ without wp_ajax_nopriv_ requiring admin-level permissions)
  4. Check for subscriber data
    Query the WordPress database for tables storing subscriber information: look for entries in wp_options with keys containing 'subscriber' or 'acx_csma', or inspect any custom tables the plugin may create
    Affected if Subscriber records containing PII (names, email addresses) exist in the database and could be returned by the vulnerable endpoint

The environment is affected if the Acurax Under Construction plugin versions 2.6 or lower is installed, the vulnerable AJAX endpoint is exposed, and subscriber data exists that could be extracted by an authenticated attacker.

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
Upgrade available Upgrade to a release after 2.6
Interim mitigation

Update the plugin to version 2.7 or later which contains the security fix; alternatively, implement proper capability checks and nonce verification on the AJAX endpoint to restrict data access to authorized administrators only.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version greater than 2.6)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Under Construction / Maintenance Mode' plugin by Acurax
  4. Check the current version number to confirm it is 2.6 or earlier
  5. Click 'Update Now' if an update is available, or manually download the latest version from the WordPress plugin repository
  6. After updating, verify the plugin is functioning correctly and subscribers can still subscribe

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

Fix this in Under Construction \/ Maintenance Mode Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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