dbcve.org
Responsive Coming Soon \& Maintenance ModeWordPress extension · Weblizar

CVE-2022-46849

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to after 1.6.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Weblizar Coming Soon Page – Responsive Coming Soon & Maintenance Mode allows SQL Injection.This issue affects Coming Soon Page – Responsive Coming Soon & Maintenance Mode: from n/a through 1.5.9.

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 confidence

A critical SQL Injection vulnerability exists in the Weblizar Coming Soon Page WordPress plugin. The flaw allows remote, unauthenticated attackers to inject malicious SQL commands via unsanitized input parameters, potentially leading to complete database compromise including data exfiltration or modification.

MitigationUpgrade to the latest version of the plugin immediately. If no patched version is available, audit the codebase for unsanitized database queries and implement prepared statements or parameterized queries.

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
Responsive Coming Soon \& Maintenance ModeWordPress extension
Affected:<= 1.6.0

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
High
Integrity
High
Availability
High

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

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 Weblizar plugin is installed
    Check the WordPress plugins directory for 'weblizar-coming-soon-page' or 'responsive-coming-soon-maintenance-mode' folder, or query the wp_plugins database table for plugin slug containing 'weblizar'
    Affected if The plugin directory or database entry exists
  2. Check installed plugin version
    Read the main plugin file header (usually index.php or main php file in the plugin folder) for the 'Version' field, or query wp_options for option_name like 'active_plugins' and check plugin files
    Affected if Version number is 1.6.0 or lower
  3. Identify vulnerable SQL query endpoints
    Search plugin PHP files for direct SQL queries using $wpdb->prepare, mysql_* functions, or unsanitized $_GET, $_POST, $_REQUEST variables used in database queries
    Affected if Unsanitized input parameters are used in SQL queries without prepared statements
  4. Confirm plugin is active on the site
    Check WordPress admin Plugins page or query wp_options table for option_name='active_plugins' and verify the Weblizar coming soon plugin is enabled
    Affected if Plugin is active and accessible to unauthenticated users

User is affected if the Weblizar Coming Soon & Maintenance Mode plugin version 1.6.0 or lower is installed and active, as unauthenticated SQL injection is possible through unsanitized input parameters in the plugin's database queries.

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 1.6.0
Interim mitigation

Upgrade to the latest version of the plugin immediately. If no patched version is available, audit the codebase for unsanitized database queries and implement prepared statements or parameterized queries.

Recommended fix High confidence

Upgrade to version 1.6.1 or later (the fixed release is 1.6.1)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find 'Responsive Coming Soon & Maintenance Mode' by Weblizar.
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version (version 1.6.1 or later contains the SQL injection fix).
  5. 5. Alternatively, you can download the latest version from the WordPress Plugin Repository and upload it manually.
  6. 6. Verify the plugin was updated successfully and test that the coming soon page functionality still works correctly.

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

Fix this in Responsive Coming Soon \& Maintenance Mode Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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