# CVE-2025-4380: Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager <= 4.89 - Unauthenticated Local File Inclusion

> Unauthenticated attackers can exploit a Local File Inclusion vulnerability in the Ads Pro WordPress plugin to execute arbitrary PHP code and read sensitive data.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-635h-h9cr-wcq9

## What is CVE-2025-4380?

CVE-2025-4380 is a high-severity path traversal vulnerability in scripteo Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager, published on 2 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2025-4380?

It affects 1 product.


Products: Scripteo Ads Pro.

## How do I fix CVE-2025-4380?

No fix has been published for CVE-2025-4380 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-4380 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4380 exists.

Public exploit code:

- https://github.com/r0otk3r/CVE-2025-4380 (github_poc): https://github.com/r0otk3r/CVE-2025-4380
- Ads Pro Plugin <= 4.89 - Local File Inclusion (nuclei): http/cves/2025/CVE-2025-4380.yaml

## Other vulnerabilities in scripteo Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager

- [CVE-2025-4689](https://insights.sbomify.com/CVE-2025-4689/): File upload in Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager (critical 9.8)
- [CVE-2025-6459](https://insights.sbomify.com/CVE-2025-6459/): Cross-site request forgery in Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager (high 8.8)
- [CVE-2025-4381](https://insights.sbomify.com/CVE-2025-4381/): Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager <= 4.89 - Unauthenticated SQL Injection (high 7.5)
- [CVE-2025-5339](https://insights.sbomify.com/CVE-2025-5339/): SQL injection in Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager (high 7.5)
- [CVE-2025-6437](https://insights.sbomify.com/CVE-2025-6437/): Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager <= 4.89 - Unauthenticated SQL Injection via oid (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4380 and fix it if it is affected.

What it is: CVE-2025-4380 is a high-severity path traversal vulnerability in scripteo Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager, published on 2 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4380 exists.

Affected product: scripteo Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-4380/ (Markdown: https://insights.sbomify.com/CVE-2025-4380/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4380
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4380
- OSV: https://osv.dev/vulnerability/CVE-2025-4380

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-4380/
Summaries are generated and may contain mistakes; the official description above is the record.