dbcve.org
Popup BuilderWordPress extension · Sygnoos

CVE-2024-2541

HIGH · 7.5 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to after 4.3.3 or later.
See remediation →
84/100
Remediation priority · High
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
The Popup Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.3.6 via the Subscribers Import feature. This makes it possible for unauthenticated attackers to extract sensitive data after an administrator has imported subscribers via a CSV file. This data may include the first name, last name, e-mail address, and potentially other personally identifiable information of subscribers.

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

The Popup Builder WordPress plugin fails to properly protect subscriber data imported via CSV. After an administrator imports subscribers using the Subscribers Import feature, the imported data (including first names, last names, email addresses, and other PII) becomes accessible to unauthenticated attackers, likely due to an insecure direct object reference or broken access control in the import functionality.

MitigationUpdate the Popup Builder plugin to the latest version beyond 4.3.6 to patch the access control vulnerability. As a temporary measure, restrict network access to the WordPress admin area and monitor logs for unauthorized access attempts to subscriber data.

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 BuilderWordPress extension
Affected:<= 4.3.3

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Popup Builder plugin is installed
    Check your WordPress installation's plugins directory or the WordPress admin plugin list for 'Popup Builder' by Sygnoos. Look for the plugin file typically located in wp-content/plugins/popup-builder/ and check the main plugin file header for the version number.
    Affected if The plugin is installed and the version is 4.3.3 or lower.
  2. Confirm the installed version against affected range
    Open the plugin's main PHP file (such as popup-builder.php) and locate the 'Version' header in the plugin comment block, or check the version displayed in the WordPress admin Plugins page.
    Affected if The installed version is 4.3.3 or any version lower than 4.3.3.
  3. Identify if subscriber import was performed
    Check your WordPress database for tables related to subscribers (commonly named wp_popup_builder_subscribers or similar). Look for recent records with import timestamps, or check the plugin's admin interface for any imported subscriber lists.
    Affected if Subscriber data exists in the database that was imported via CSV, indicating the import feature was used.
  4. Test unauthenticated access to subscriber data
    Attempt to access common subscriber data endpoints or API routes used by the plugin without providing authentication credentials. This may include checking URLs like /wp-json/popup-builder/v1/subscribers, /?pba=subscribers, or similar endpoints the plugin exposes. Use a tool like curl or a browser to send unauthenticated requests.
    Affected if Subscriber data (names, emails, PII) is returned in the response without requiring login authentication.

You are affected if the Popup Builder plugin version is 4.3.3 or lower AND subscriber data was imported via CSV AND that data is accessible without authentication.

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

Update the Popup Builder plugin to the latest version beyond 4.3.6 to patch the access control vulnerability. As a temporary measure, restrict network access to the WordPress admin area and monitor logs for unauthorized access attempts to subscriber data.

Recommended fix High confidence

Latest version of Popup Builder plugin (version 4.3.7 or higher)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Popup Builder plugin
  4. 4. Check the current version number
  5. 5. If the installed version is 4.3.6 or below, update the plugin to the latest available version
  6. 6. After updating, verify the Subscribers Import feature is functioning correctly and review subscriber data for any unauthorized access

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

Fix this in Popup Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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