dbcve.org
Ads ProWordPress extension · Scripteo

CVE-2024-13322

HIGH · 7.5 CVSS v3.1 Published 2025-05-02
Fix available
A fix is available. Upgrade to 4.89 or later.
See remediation →
84/100
Remediation priority · High
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 SQL Injection via the 'a_id' parameter in all versions up to, and including, 4.88 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 confidence

The Ads Pro Plugin for WordPress is vulnerable to SQL Injection via the 'a_id' parameter in versions up to 4.88. The vulnerability exists due to insufficient escaping of user-supplied input combined with lack of prepared statements in the SQL query, allowing unauthenticated attackers to inject malicious SQL queries and extract sensitive database information.

MitigationUpdate the Ads Pro Plugin to a version beyond 4.88 that includes proper input sanitization and uses prepared statements for all SQL queries. If no update is available, consider disabling the plugin temporarily until a patch is released.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Ads Pro plugin is installed
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for 'ads-pro' or similar plugin folder. Check the plugin's main PHP file for the version header (typically in plugin comments at the top of the main file).
    Affected if The plugin is present and the version displayed is 4.88 or lower (or any version below 4.89).
  2. Confirm plugin is active
    In WordPress admin, check the Plugins list to see if Ads Pro is currently activated. Alternatively, query the wp_options table for the 'active_plugins' option.
    Affected if The plugin is activated on the WordPress site.
  3. Identify vulnerable parameter usage
    Review web server access logs (Apache/nginx) for requests to the WordPress site containing 'a_id' parameter in the query string. Search for patterns like '?a_id=' in URLs.
    Affected if The site processes requests with the 'a_id' parameter, indicating the vulnerable code path is reachable.
  4. Check for signs of exploitation
    Analyze database query logs or web application firewall (WAF) logs for suspicious SQL patterns within 'a_id' values, such as UNION SELECT, OR 1=1, or other SQL injection payloads.
    Affected if Malicious SQL injection attempts are found in logs targeting the 'a_id' parameter.

The environment is affected if the Ads Pro plugin is installed with version 4.88 or lower, is currently active, and the site processes requests through the vulnerable 'a_id' parameter.

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 4.89 or later
Fixed in 4.89
Interim mitigation

Update the Ads Pro Plugin to a version beyond 4.88 that includes proper input sanitization and uses prepared statements for all SQL queries. If no update is available, consider disabling the plugin temporarily until a patch is released.

Recommended fix High confidence

Ads Pro Plugin version 4.89

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Ads Pro Plugin - Multi-Purpose WordPress Advertising Manager' plugin
  4. If an update is available, click 'Update Now' to upgrade to version 4.89
  5. Alternatively, manually download version 4.89 from CodeCanyon and upload via Plugins > Add New > Upload Plugin
  6. Verify the plugin version is now 4.89 after updating

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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