Cm PopupWordPress extension · Cminds

CVE-2023-30750

HIGH · 8.1 CVSS v3.1 Published 2023-12-20

Fix available

A fix is available. Upgrade to 1.6.0 or later.

See remediation →

87/100

Remediation priority · High

Remotely reachable Zero-click

Official description

NVD · unedited

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in CreativeMindsSolutions CM Popup Plugin for WordPress.This issue affects CM Popup Plugin for WordPress: from n/a through 1.5.10.

Technical summary

dbcve analysis · high confidence

SQL Injection vulnerability in CM Popup Plugin for WordPress allows attackers to inject malicious SQL commands via unsanitized input parameters in database queries. The vulnerability exists in versions up to and including 1.5.10, potentially allowing unauthorized data access or modification.

MitigationUpdate to the latest version of CM Popup Plugin which contains proper input sanitization and parameterized SQL queries. If no update is available, implement input validation and use WordPress prepared statements ($wpdb->prepare) for all database queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Cm PopupWordPress extension

Affected:< 1.6.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify CM Popup plugin is installed

Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Cminds Cm Popup' or 'CM Popup' in the list

Affected if plugin is not found in the installed plugins list
Check the installed version number

In the plugins list, locate the version number displayed beneath the plugin name 'Cminds Cm Popup'

Affected if version displayed is 1.5.10 or lower, or any version number less than 1.6.0
Confirm plugin is active

In WordPress admin > Plugins, check if the plugin shows as 'Active' (not 'Inactive' or 'Must Use')

Affected if plugin is active and version is below 1.6.0
Verify vulnerable SQL query patterns exist (optional advanced check)

If you have file access, examine plugin PHP files in wp-content/plugins/cm-popup for unsanitized SQL queries using $wpdb->prepare without proper sanitization, or direct query concatenation with $_POST/$_GET/$_REQUEST parameters

Affected if plugin version is below 1.6.0 AND unsanitized database queries are found in the plugin code

A user is affected if the CM Popup plugin is installed, active, and running version 1.5.10 or any version lower than 1.6.0

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.6.0 or later

Fixed in 1.6.0

Interim mitigation

Update to the latest version of CM Popup Plugin which contains proper input sanitization and parameterized SQL queries. If no update is available, implement input validation and use WordPress prepared statements ($wpdb->prepare) for all database queries.

Recommended fix High confidence

1.6.0

Create a full backup of your WordPress site (database and files) before updating any plugins
Log in to the WordPress admin dashboard
Navigate to Plugins > Installed Plugins
Locate the CM Popup (CM Popup Plugin for WordPress) in the plugin list
If an update is available, click 'Update Now' to upgrade to version 1.6.0, or manually upload version 1.6.0 if the automatic update is not showing
After updating, verify the plugin is running version 1.6.0 by checking the Plugins page
Test the popup functionality on your site to ensure the plugin is working correctly after the update

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

Fix this in Cm Popup Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing5.0 h
Review / QA3.0 h

17.0 hours of engineering $2,970

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30750 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-30750?

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.

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

At a glance

A fix existsUpgrade to 1.6.0 or later

Severity 8.1 High

Exploit likelihood EPSS, next 30 days 0.6%

Affects: Cm Popup

Remediation

A high-priority fix

Fix this in Cm Popup 17 hrs · Moderate

Typical engagement from $2,970

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2023-30750 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References