dbcve.org
Ads ProWordPress extension · Scripteo

CVE-2025-4380

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-02
Fix available
A fix is available. Upgrade to after 4.89 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
The Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.89 via the 'bsa_template' parameter of the `bsa_preview_callback` function. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases .php files can can be uploaded and included, or already exist on the site.

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 plugin versions up to 4.89 contains an unauthenticated Local File Inclusion vulnerability in the bsa_preview_callback function via the bsa_template parameter. Attackers can include arbitrary files from the server filesystem, potentially executing uploaded PHP code or existing PHP files to achieve remote code execution.

MitigationUpdate the Ads Pro plugin to version 4.90 or later which contains the patch for this vulnerability. If immediate update is not possible, disable the plugin or restrict access to the affected endpoint via WAF rules until patching can be completed.

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
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. Identify the installed version of the Ads Pro plugin
    Locate the plugin in wp-content/plugins/ and open its main PHP file to read the Version header in the plugin comment block, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name LIKE '%ads_pro%' and option_name LIKE '%version%';
    Affected if The version number returned is 4.89 or lower, or if the version cannot be determined and the plugin is present
  2. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify Ads Pro is activated, or query: SELECT * FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin appears in the active_plugins list
  3. Verify the vulnerable bsa_preview_callback function exists
    Search the plugin files for 'bsa_preview_callback' function definition, typically in the main plugin file or includes/preview.php, using grep or file search within wp-content/plugins/ads-pro/
    Affected if The function bsa_preview_callback is found in the plugin code, indicating the vulnerable code is present
  4. Check if the bsa_template parameter is handled without sanitization
    Locate the code handling the bsa_template parameter (search for $_GET['bsa_template'] or $_POST['bsa_template']) and verify if it uses include(), require(), or similar functions without proper path sanitization
    Affected if The bsa_template parameter is processed through include/require without sanitizing directory traversal characters (..) or restricting to allowed paths
  5. Test if the endpoint is externally accessible
    Send a request to the AJAX endpoint or preview URL that triggers bsa_preview_callback, such as: wp-admin/admin-ajax.php?action=bsa_preview&bsa_template=../../../../wp-config.php (using a known valid action name from the plugin)
    Affected if The server responds without proper authentication or access control, allowing unauthenticated access to the file inclusion mechanism

A system is affected if the Ads Pro plugin version is 4.89 or lower AND the plugin is active AND the vulnerable bsa_preview_callback function with the bsa_template parameter is present in the code, allowing unauthenticated local file inclusion.

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 the Ads Pro plugin to version 4.90 or later which contains the patch for this vulnerability. If immediate update is not possible, disable the plugin or restrict access to the affected endpoint via WAF rules until patching can be completed.

Recommended fix High confidence

4.90 or later

  1. Backup the WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Ads Pro: Multi-Purpose WordPress Advertising Manager plugin
  4. Check the current installed version (should be <= 4.89)
  5. Update the plugin to the latest available version (4.90 or higher) by clicking Update Now
  6. Alternatively, download the latest version from the vendor (CodeCanyon) and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number reflects the update
  8. Confirm the site functions normally after the update

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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