dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-8877

HIGH · 7.5 CVSS v3.1 Published 2025-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 AffiliateWP plugin for WordPress is vulnerable to SQL Injection via the ajax_get_affiliate_id_from_login function in all versions up to, and including, 2.28.2 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 AffiliateWP WordPress plugin is vulnerable to SQL Injection in the ajax_get_affiliate_id_from_login AJAX function in all versions up to 2.28.2. The vulnerability stems from insufficient escaping of user-supplied input combined with missing prepared statements in the SQL query, allowing unauthenticated attackers to inject arbitrary SQL commands and extract sensitive data from the database.

MitigationUpdate AffiliateWP to version 2.28.3 or later to remediate this SQL injection vulnerability. As a stopgap, disable the affected AJAX endpoint via web server configuration until the patch can be applied.

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 checks

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

  1. Confirm AffiliateWP plugin is installed
    Navigate to WordPress admin Plugins page or check /wp-content/plugins/ directory for affiliatewp folder
    Affected if The affiliatewp folder does not exist in the plugins directory
  2. Identify installed AffiliateWP version
    Check the plugin version in WordPress admin (Plugins > AffiliateWP) or read the main plugin file header at /wp-content/plugins/affiliatewp/includes/class-affiliate-wp.php
    Affected if Version is 2.28.2 or lower (the plugin version is not 2.28.3 or higher)
  3. Verify the plugin is active
    In WordPress admin, confirm AffiliateWP status shows as Active; inactive plugins cannot be exploited via AJAX
    Affected if Plugin is active and running
  4. Confirm the ajax_get_affiliate_id_from_login function exists
    Search plugin source code in /wp-content/plugins/affiliatewp/includes/ for 'ajax_get_affiliate_id_from_login' or review the file that registers this AJAX action
    Affected if The vulnerable AJAX function is present in the plugin code (function exists in version 2.28.2 or lower)

You are affected if AffiliateWP is installed, active, and the version is 2.28.2 or lower, allowing the unauthenticated SQL injection via the ajax_get_affiliate_id_from_login AJAX endpoint.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update AffiliateWP to version 2.28.3 or later to remediate this SQL injection vulnerability. As a stopgap, disable the affected AJAX endpoint via web server configuration until the patch can be applied.

Recommended fix Moderate confidence

Upgrade to any version of AffiliateWP higher than 2.28.2

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate AffiliateWP in the plugin list
  4. Check the current installed version to confirm it is 2.28.2 or lower
  5. Update the plugin to the latest available version from the WordPress plugin repository or your license source
  6. Verify the update completes successfully
  7. Confirm the new version is higher than 2.28.2
Caveat Review the plugin's changelog for any breaking changes or feature modifications before updating in production environments

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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