dbcve.org
Popup BuilderWordPress extension · Sygnoos

CVE-2019-14695

CRITICAL · 9.8 CVSS v3.1 Published 2019-08-06
Fix available
A fix is available. Upgrade to 3.45 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
A SQL injection vulnerability exists in the Sygnoos Popup Builder plugin before 3.45 for WordPress. Successful exploitation of this vulnerability would allow a remote attacker to execute arbitrary SQL commands on the affected system via com/libs/Table.php because Subscribers Table ordering is mishandled.

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

A SQL injection vulnerability exists in the Sygnoos Popup Builder WordPress plugin versions prior to 3.45. The vulnerability is located in com/libs/Table.php where the Subscribers Table ordering functionality improperly handles user input, allowing remote attackers to inject arbitrary SQL commands.

MitigationUpdate the Sygnoos Popup Builder plugin to version 3.45 or later. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to mitigate SQL injection attempts.

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:< 3.45

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. Locate the Popup Builder plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'popup-builder', 'sg-popup', or similar Sygnoos Popup Builder plugin directory
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open the main plugin file (usually popup-builder.php or readme.txt) and locate the 'Version' header in the plugin metadata
    Affected if The version number found is less than 3.45 (e.g., 3.44, 3.40, etc.)
  3. Verify the vulnerable file exists
    Locate the file com/libs/Table.php within the plugin directory and confirm it is present
    Affected if The Table.php file exists in the plugin installation
  4. Check if Subscribers functionality is accessible
    Verify the WordPress admin panel includes access to the Subscribers feature under the Popup Builder menu, which triggers the ordering functionality in Table.php
    Affected if The Subscribers table feature is enabled and accessible in the WordPress admin area

Your environment is affected if the Sygnoos Popup Builder plugin is installed with a version lower than 3.45 and the com/libs/Table.php file is present with the Subscribers ordering feature accessible.

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

Update the Sygnoos Popup Builder plugin to version 3.45 or later. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to mitigate SQL injection attempts.

Recommended fix High confidence

Popup Builder plugin version 3.45 or later

  1. Create a complete backup of your WordPress site (database and files) before making any changes
  2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  3. Locate the Popup Builder plugin by Sygnoos
  4. Click 'Update now' if an update is available, or manually upload version 3.45 or later of the Popup Builder plugin
  5. Verify the plugin version is 3.45 or higher after updating
  6. Check the Subscribers Table functionality to ensure the plugin is functioning correctly after the update
  7. Review access logs for any signs of exploitation attempts targeting the com/libs/Table.php endpoint

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

Fix this in Popup Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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