CVE-2025-7402
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 · uneditedThe Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager plugin for WordPress is vulnerable to time-based SQL Injection via the ‘site_id’ parameter in all versions up to, and including, 4.95 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe Ads Pro WordPress plugin (versions up to 4.95) contains an unauthenticated time-based SQL injection vulnerability in the 'site_id' parameter. The plugin fails to properly escape user input and lacks prepared statements, allowing attackers to inject arbitrary SQL queries into existing database calls to exfiltrate sensitive data.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify Ads Pro plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Ads Pro' in the list. Alternatively, check the /wp-content/plugins/ directory for the ads-pro folder.Affected if Ads Pro plugin is present in the WordPress installation
-
Determine installed plugin versionIn the WordPress plugins list, click on the plugin to view its details, or check the main plugin file header in /wp-content/plugins/ads-pro/ads-pro.php for the 'Version' comment tag.Affected if Version is 4.95 or lower (the fixed version is 4.96)
-
Confirm site_id parameter is accessibleIdentify endpoints that accept a 'site_id' parameter. For unauthenticated SQLi, this is typically a public-facing URL such as ?page_id=X&site_id=Y or similar query strings used by the plugin's shortcodes or AJAX handlers. Check plugin documentation or inspect plugin files for site_id usage.Affected if The plugin processes the 'site_id' parameter without authentication and uses it in database queries
-
Check for unusual database activityReview MySQL slow query logs or general logs for time-based injection patterns (e.g., SLEEP(), BENCHMARK() functions in SQL queries originating from the web server). Also check for unexpected new admin users or modified content in the wp_posts and wp_options tables.Affected if Suspicious SQL patterns found in logs or unauthorized database changes detected
You are affected if the Ads Pro plugin versions 4.95 or lower are installed and active, with the site_id parameter exposed and processing user input.
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 the Ads Pro plugin to version 4.96 or higher immediately. If immediate updating is not feasible, implement WAF rules to block or sanitize requests containing malicious 'site_id' parameter values, and conduct a database audit for signs of compromise.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7402 — 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-7402 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