Ads ProWordPress extension · Scripteo
CVE-2025-4381
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 SQL Injection via the ‘$id’ variable of the getSpace() function in all versions up to, and including, 4.89 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 Plugin for WordPress is vulnerable to SQL Injection in the getSpace() function. The $id parameter is not properly escaped and the SQL query lacks prepared statements, allowing unauthenticated attackers to inject arbitrary SQL commands to extract sensitive database information.
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
<= 4.89CVSS 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 installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Ads Pro' or 'Scripteo Ads Pro' in the list of installed plugins.Affected if The plugin appears in the installed plugins list.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Ads Pro, and view the version number displayed beneath the plugin name. Alternatively, check the plugin main file header in wp-content/plugins/ads-pro-plugin or similar path for the Version field.Affected if The installed version is 4.89 or lower.
-
Confirm plugin is activeIn WordPress admin > Plugins > Installed Plugins, verify that Ads Pro shows as 'Active' rather than 'Inactive'.Affected if The plugin is currently active.
-
Identify exposed endpointThe vulnerability exists in the getSpace() function. Determine if any public-facing shortcode, widget, or AJAX endpoint that calls this function is in use. Check the plugin settings for enabled ad spaces and review published pages using Ads Pro shortcodes.Affected if Ad spaces are configured and exposed via shortcodes or widgets on the site.
If Ads Pro plugin is installed, active, and running version 4.89 or lower with configured ad spaces, the environment is affected by this SQL Injection vulnerability.
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 plugin to version 4.90 or later where the vulnerability is patched. If no update is available, disable the plugin immediately.
Fix this in Ads Pro
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4381 — 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-4381 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