dbcve.org
Wp Popup BannersWordPress extension · Wp Popup Banners Project

CVE-2023-1471

MEDIUM · 6.5 CVSS v3.1 Published 2023-03-17
Fix available
A fix is available. Upgrade to after 1.2.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 WP Popup Banners plugin for WordPress is vulnerable to SQL Injection via the 'banner_id' parameter in versions up to, and including, 1.2.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers with minimal permissions, such as a subscriber, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The WP Popup Banners plugin for WordPress versions up to 1.2.5 contains a SQL Injection vulnerability in the 'banner_id' parameter. The code fails to properly escape user input and lacks prepared statements, allowing authenticated attackers with subscriber-level permissions to inject arbitrary SQL queries and extract sensitive database information.

MitigationUpdate the WP Popup Banners plugin to the latest version once available, or disable the plugin until a patch is released. The fix requires implementing proper SQL escaping and $wpdb->prepare() statements for the banner_id parameter.

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
Wp Popup BannersWordPress extension
Affected:<= 1.2.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 WP Popup Banners plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WP Popup Banners' or 'Wp Popup Banners' in the plugin list.
    Affected if Plugin is listed in the installed plugins, regardless of activation status
  2. Identify installed plugin version
    In the Plugins list, locate the WP Popup Banners entry and note the version number displayed below the plugin name. Alternatively, access via FTP/SFTP and read the plugin header in /wp-content/plugins/wp-popup-banners/index.php or similar main file.
    Affected if Version number is 1.2.5 or lower (any version up to and including 1.2.5)
  3. Confirm plugin is active
    In WordPress admin > Plugins, check if WP Popup Banners shows as 'Active' under the plugin status column.
    Affected if Plugin is currently active on the site
  4. Verify subscriber-level accounts exist
    In WordPress admin > Users, review the user list to see if any accounts with 'Subscriber' role exist. Click on a user to confirm their role if unsure.
    Affected if One or more subscriber-level user accounts exist on the site (any authenticated user with subscriber role can exploit this vulnerability)
  5. Check for banner_id parameter usage
    Inspect network traffic or server logs when accessing any popup banner functionality. The vulnerable parameter is 'banner_id' used in the plugin's frontend or admin AJAX handlers.
    Affected if The plugin processes requests containing a 'banner_id' parameter without proper sanitization

A site is affected if WP Popup Banners plugin version 1.2.5 or lower is installed and active, and the site has at least one subscriber-level user account.

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.

From vendor data
Upgrade available Upgrade to a release after 1.2.5
Interim mitigation

Update the WP Popup Banners plugin to the latest version once available, or disable the plugin until a patch is released. The fix requires implementing proper SQL escaping and $wpdb->prepare() statements for the banner_id parameter.

Fix this in Wp Popup Banners Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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