dbcve.org
Ads ProWordPress extension · Scripteo

CVE-2025-5339

HIGH · 7.5 CVSS v3.1 Published 2025-07-02
Fix available
A fix is available. Upgrade to after 4.89 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 Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager plugin for WordPress is vulnerable to time-based SQL Injection via the ‘bsa_pro_id’ parameter in all versions up to, and including, 4.89 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers 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 Ads Pro Plugin for WordPress is vulnerable to time-based SQL injection via the 'bsa_pro_id' parameter in versions up to 4.89. The plugin fails to properly escape user input and does not use prepared statements, allowing unauthenticated attackers to inject arbitrary SQL queries to extract sensitive data.

MitigationUpdate the plugin to version 4.90 or later. If an update is unavailable, disable the plugin or implement a web application firewall (WAF) rule to block SQL injection attempts targeting the 'bsa_pro_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
Ads ProWordPress extension
Affected:<= 4.89

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 Ads Pro plugin is installed
    Navigate to WordPress admin > Plugins or inspect wp-content/plugins/ directory for folders containing 'ads-pro', 'ads-pro-plugin', or similar naming. Check for a plugin named 'Ads Pro' or 'Scripteo Ads Pro'.
    Affected if The plugin is present in the plugins directory and shows as installed in WordPress.
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find Ads Pro. The version number is displayed below the plugin name. Alternatively, open the main plugin PHP file (usually ads-pro.php or similar) and look for the 'Version' header in the plugin comment block.
    Affected if The displayed version number is 4.89 or lower.
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Ads Pro plugin shows as 'Active' (not deactivated or inactive).
    Affected if The plugin is currently activated on the WordPress site.
  4. Identify if vulnerable parameter is processed
    Review the site for any pages or AJAX endpoints that accept a 'bsa_pro_id' parameter. Common paths include frontend ad display pages, AJAX handlers, or API endpoints. Use browser developer tools or check plugin code for forms/links containing 'bsa_pro_id'.
    Affected if The plugin processes the 'bsa_pro_id' parameter in any publicly accessible functionality.

You are affected if Ads Pro plugin version 4.89 or lower is installed, activated, and the site processes the 'bsa_pro_id' parameter in any accessible functionality.

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

Update the plugin to version 4.90 or later. If an update is unavailable, disable the plugin or implement a web application firewall (WAF) rule to block SQL injection attempts targeting the 'bsa_pro_id' parameter.

Fix this in Ads Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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