dbcve.org
Ads ProWordPress extension · Scripteo

CVE-2025-4689

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 which leads to Remote Code Execution in all versions up to, and including, 4.89. This is due to the presence of a SQL Injection vulnerability and Local File Inclusion vulnerability that can be chained with an image upload. This makes it possible for unauthenticated attackers to execute code on the server upload image files on the server than can be fetched via a SQL injection vulnerability, and ultimately executed as PHP code through the local file inclusion vulnerability.

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 a critical vulnerability chain allowing unauthenticated Remote Code Execution. Attackers exploit a SQL Injection to retrieve file paths of uploaded images, then use a Local File Inclusion flaw to execute those images as PHP code, achieving full server compromise.

MitigationImmediately update the Ads Pro plugin to the latest patched version once available, or implement a WAF rule to block SQLi/LFI attack patterns and disable the plugin until patched. Consider removing unused plugin functionality related to file uploads.

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. Verify Ads Pro plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Ads Pro - Multi-Purpose Ad Manager' and check the version number displayed under the plugin name
    Affected if The installed version is 4.89 or lower (any version up to and including 4.89)
  2. Confirm plugin is active
    Check if the Ads Pro plugin shows as 'Active' in the WordPress plugins list
    Affected if The plugin is active and running - inactive plugins cannot be exploited
  3. Inspect plugin file structure
    Access the WordPress filesystem via FTP or file manager, navigate to /wp-content/plugins/ads-pro-plugin/ and list the main plugin files
    Affected if The plugin directory exists and contains the vulnerable file upload handling code
  4. Review web server access logs
    Examine Apache/nginx access logs for SQL injection patterns (e.g., UNION SELECT, information_schema) or LFI patterns (e.g., ../../..) targeting plugin endpoints
    Affected if Suspicious SQLi or LFI requests are found in logs targeting Ads Pro endpoints
  5. Check upload directories
    Inspect /wp-content/uploads/ads-pro/ or similar upload paths used by the plugin for any unexpected PHP files masquerading as images
    Affected if PHP files exist in upload directories that were not intentionally placed there, indicating successful exploitation

You are affected if the Ads Pro plugin version is 4.89 or lower and the plugin is currently active - the vulnerability can be exploited without authentication.

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

Immediately update the Ads Pro plugin to the latest patched version once available, or implement a WAF rule to block SQLi/LFI attack patterns and disable the plugin until patched. Consider removing unused plugin functionality related to file uploads.

Recommended fix Moderate confidence

Update to version 4.90 or later (any version higher than 4.89)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Ads Pro: Multi-Purpose WordPress Advertising Manager plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, download the latest version from the plugin provider and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 4.90 or higher

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

Fix this in Ads Pro Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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