dbcve.org
Ads ProWordPress extension · Scripteo

CVE-2025-6459

HIGH · 8.8 CVSS v3.1 Published 2025-07-02
Fix available
A fix is available. Upgrade to after 4.89 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Cross-Site Request Forgery in all versions up to, and including, 4.89. This is due to missing or incorrect nonce validation on the bsaCreateAdTemplate function. This makes it possible for unauthenticated attackers to inject and execute arbitrary PHP code via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 WordPress advertising plugin versions up to 4.89 lack proper nonce validation in the bsaCreateAdTemplate function, enabling CSRF attacks. Attackers can exploit this to inject and execute arbitrary PHP code by tricking authenticated administrators into clicking crafted links.

MitigationUpdate to version 4.90 or later where nonce validation has been implemented. If updates are unavailable, disable the plugin immediately and audit for signs of compromise.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Ads Pro plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Ads Pro' or 'Scripteo Ads Pro' in the list
    Affected if Plugin is not present in the installed plugins list (not affected)
  2. Identify installed version number
    In the Plugins list, look at the version number displayed below the plugin name 'Ads Pro' or click on the plugin to view details
    Affected if Version number is 4.89 or lower, indicating the plugin lacks nonce validation in bsaCreateAdTemplate
  3. Locate vulnerable function in plugin code
    Access site files via FTP or File Manager, navigate to /wp-content/plugins/ads-pro/plugin-ads-pro.php and search for 'bsaCreateAdTemplate' function definition
    Affected if Function bsaCreateAdTemplate exists in the plugin file
  4. Verify nonce validation presence
    Within the bsaCreateAdTemplate function, search for 'wp_verify_nonce' or 'check_admin_referer' calls. Review the function code around lines where user input is processed
    Affected if The bsaCreateAdTemplate function exists but contains NO nonce verification calls (wp_verify_nonce, check_admin_referer, etc.) near the beginning of the function

User is affected if Ads Pro plugin version is 4.89 or lower AND the bsaCreateAdTemplate function lacks nonce validation, meaning an authenticated administrator could be tricked into executing arbitrary PHP code via CSRF.

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.89
Interim mitigation

Update to version 4.90 or later where nonce validation has been implemented. If updates are unavailable, disable the plugin immediately and audit for signs of compromise.

Recommended fix Moderate confidence

Version 4.90 or later (check WordPress plugin repository or vendor for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager
  4. Check the current version installed (should be 4.89 or below)
  5. Deactivate the plugin before updating
  6. Click 'Update Now' when an update is available, or manually download the latest version from the vendor
  7. Activate the updated plugin after installation
  8. Verify the plugin is running version 4.90 or higher after update
Caveat Review plugin settings after upgrade as minor configuration adjustments may be needed

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

Fix this in Ads Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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