CVE-2025-30628
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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in AA-Team Amazon Affiliates Addon for WPBakery Page Builder (formerly Visual Composer) allows SQL Injection.This issue affects Amazon Affiliates Addon for WPBakery Page Builder (formerly Visual Composer): from n/a through 1.2.
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 confidenceSQL Injection vulnerability in AA-Team Amazon Affiliates Addon for WPBakery Page Builder allows attackers to inject malicious SQL commands through unsanitized user inputs. The vulnerability affects the plugin from unspecified versions through version 1.2, potentially exposing sensitive database contents including affiliate data and user information.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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.
-
Locate the AA-Team Amazon Affiliates pluginInspect the WordPress plugins directory (wp-content/plugins/) for a folder containing 'aa-team' and 'amazon-affiliates' or similar naming. Check the plugin's main PHP file for the version declared in the plugin header comment.Affected if The plugin folder exists in the WordPress plugins directory.
-
Determine the installed versionOpen the plugin's main file (usually the primary PHP file in the plugin folder) and locate the Version line in the plugin header comment, or check the readme.txt file for the version field.Affected if The reported version is 1.2 or any lower version number.
-
Verify the plugin is activeLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Confirm whether the AA-Team Amazon Affiliates Addon is listed as Active, or query the wp_options table for the active_plugins option.Affected if The plugin appears as Activated or is present in the active_plugins WordPress option.
-
Check for user-facing input formsInspect the plugin files for any $_GET, $_POST, or $_REQUEST superglobal usage without proper sanitization functions (such as prepare(), esc_sql(), or parameterized queries). Focus on files handling search, filtering, or submission features.Affected if The plugin accepts user input through query parameters or form submissions and uses that input directly in SQL queries.
You are affected if the AA-Team Amazon Affiliates Addon plugin is installed, active, and runs version 1.2 or lower, especially if the plugin exposes any user input fields that interact with the database.
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 the latest version of the plugin if a patched release is available; otherwise, disable or remove the plugin until remediation is possible. Implement parameterized queries or proper input sanitization as a permanent fix.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30628 — 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-30628 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