CVE-2025-46444
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in scripteo Ads Pro ap-plugin-scripteo allows PHP Local File Inclusion.This issue affects Ads Pro: from n/a through <= 4.89.
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 · moderate confidenceLocal File Inclusion vulnerability in scripteo Ads Pro plugin (ap-plugin-scripteo) allows attackers to include arbitrary PHP files from the server via improper control of filename in include/require statements. This can lead to remote code execution if attacker can control the included file path or if sensitive local files contain PHP code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if scripteo Ads Pro plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'scripteo Ads Pro' or 'ap-plugin-scripteo'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'ap-plugin-scripteo' or similar.Affected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin, find the plugin in the plugins list and check the version number displayed beneath the plugin name. Alternatively, inspect the main plugin PHP file (usually found in the plugin directory) for a version comment or define statement.Affected if The version cannot be determined or is earlier than the patched release
-
Inspect for vulnerable file inclusion codeExamine PHP files within the plugin directory, particularly those handling include/require statements. Look for code that uses user-supplied input (GET/POST parameters, request variables) directly in include, require, include_once, or require_once statements without proper sanitization.Affected if Files contain include/require statements that incorporate unsanitized user input in the file path
-
Check if the vulnerable parameter is accessibleIf vulnerable code is found, identify the affected parameter name (e.g., a parameter used in the include/require) and test whether it can be manipulated via HTTP requests to the affected URL endpoint.Affected if The vulnerable parameter can be accessed and manipulated through web requests
A user is affected if the scripteo Ads Pro plugin is installed AND contains code that uses unsanitized user input in include/require statements, allowing arbitrary file inclusion.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of Ads Pro plugin; if unavailable, disable the plugin. Implement strict allowlist-based input validation on all file inclusion paths and avoid user-supplied input in include/require statements.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46444 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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