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

Q: 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.

Q: Is CVE-2025-4380 being exploited?

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

Q: 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.

High 8.1 Published 2 Jul 2025 Updated 8 Apr 2026

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

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

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

Which versions are affected by CVE-2025-4380?

It affects 1 product.

Products include 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.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

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: 1 Nuclei template and 1 proofs of concept on GitHub.

Sources

Also known as GHSA-635h-h9cr-wcq9.