dbcve.org
Popup MakerWordPress extension · Code Atlantic

CVE-2024-47358

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 1.20.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
Missing Authorization vulnerability in Daniel Iser Popup Maker popup-maker.This issue affects Popup Maker: from n/a through <= 1.19.2.

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 Missing Authorization vulnerability in Popup Maker plugin versions up to 1.19.2 allows attackers to bypass access controls due to missing capability checks on certain functionality, potentially enabling unauthenticated or unauthorized users to perform actions they should not have permission to execute.

MitigationUpdate Popup Maker to the latest version which includes proper authorization/capability checks, or manually add appropriate current_user_can() checks and nonce verification to the affected plugin functions.

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
Popup MakerWordPress extension
Affected:< 1.20.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 Popup Maker plugin is installed
    Check your WordPress site's wp-content/plugins/ directory for the 'popup-maker' folder, or view the installed plugins list in the WordPress admin dashboard under Plugins
    Affected if Popup Maker plugin folder or entry exists in the WordPress plugins directory
  2. Check installed Popup Maker version
    In WordPress admin, go to Plugins > Popup Maker and note the version number displayed, or inspect the main plugin file (popup-maker.php) and look for the 'Version:' header comment
    Affected if The installed version number is less than 1.20.0 (for example: 1.19.2, 1.18.0, 1.17.5, etc.)
  3. Identify plugin access points
    Review the popup-maker plugin directory for PHP files containing AJAX handlers, admin pages, or public-facing endpoints. Look for functions that process user requests without current_user_can() capability checks
    Affected if The plugin contains functionality that processes requests without verifying user capabilities (this requires code review as specific vulnerable functions are not publicly documented)
  4. Test for unauthorized access
    If possible, use a tool like Burp Suite or curl to send requests to Popup Maker AJAX endpoints or admin actions while logged in as a low-privilege user (subscriber or no role) and observe if actions succeed without proper authorization headers
    Affected if A user without administrator privileges can successfully execute actions that should require higher-level capabilities

You are affected if Popup Maker plugin is installed and the version is less than 1.20.0, as this version range contains the missing authorization vulnerability in certain plugin functions.

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 1.20.0 or later
Fixed in 1.20.0
Interim mitigation

Update Popup Maker to the latest version which includes proper authorization/capability checks, or manually add appropriate current_user_can() checks and nonce verification to the affected plugin functions.

Recommended fix High confidence

1.20.0

  1. Update the Popup Maker plugin to version 1.20.0 or higher via the WordPress admin dashboard (Plugins > Updates), or via WP-CLI: wp plugin update popup-maker

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

Fix this in Popup Maker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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