dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7330

HIGH · 7.2 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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 Auto Affiliate Links plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 6.8.8 This is due to insufficient input sanitization on the 'url' POST parameter in the aal_url_stats_save_action() function and a complete absence of output escaping in aal_display_clicks(), where the stored value is echoed directly into an anchor element's href attribute and inner text without esc_url(), esc_attr(), or esc_html(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts into the admin statistics page that execute in an administrator's browser when the page is visited, leveraging a publicly exposed nonce and an unauthenticated AJAX endpoint registered via the wp_ajax_nopriv_ hook.

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 Auto Affiliate Links WordPress plugin (versions up to 6.8.8) contains a stored XSS vulnerability. An unauthenticated attacker can inject malicious JavaScript via the 'url' POST parameter to an unauthenticated AJAX endpoint (wp_ajax_nopriv_) that has a publicly exposed nonce. The injected payload is stored and later executed when an administrator visits the statistics page, as the URL value is rendered directly into an anchor element's href and inner text without any output escaping (esc_url, esc_attr, or esc_html).

MitigationUpgrade to a patched version of the plugin that implements proper input sanitization on the 'url' parameter and adds output escaping (esc_url, esc_attr, esc_html) in aal_display_clicks(). Also audit and clean any existing malicious entries in the database.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 Auto Affiliate Links plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Auto Affiliate Links' in the list. Note the version number displayed.
    Affected if Plugin is installed and version is 6.8.8 or lower (versions up to and including 6.8.8 are affected)
  2. Confirm the plugin is active
    In the Plugins page, check if Auto Affiliate Links shows as 'Active' under the plugin name.
    Affected if Plugin is active and version is 6.8.8 or lower - the vulnerability requires the plugin to be active to be exploitable
  3. Inspect the database for suspicious URL entries
    Query your WordPress database: SELECT * FROM wp_options WHERE option_name LIKE '%aal%' OR query the plugin's links table (commonly wp_auto_affiliate_links or similar) for entries containing script tags, javascript:, or onload attributes in the url field.
    Affected if Any records exist with malicious JavaScript payloads in url fields (indicates active exploitation)
  4. Verify the vulnerable AJAX endpoint is accessible
    Send a POST request to /wp-admin/admin-ajax.php with action=nopriv_aal_save_link (or the plugin's specific AJAX action for saving links) - use a tool like curl or Burp. Also check if the nonce is exposed in page source of public pages.
    Affected if The endpoint responds and accepts unauthenticated requests with a predictable or exposed nonce
  5. Review the aal_display_clicks function source code
    In the plugin files (wp-content/plugins/auto-affiliate-links/), locate the aal_display_clicks function and verify whether esc_url, esc_attr, or esc_html are used when outputting the URL value into the HTML anchor element.
    Affected if The function outputs the URL without any escaping functions - the raw url value is placed in both href and link text

A defender is affected if the Auto Affiliate Links plugin is active at version 6.8.8 or lower, the database contains malicious URL entries, or the source code lacks output escaping in the aal_display_clicks function.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the plugin that implements proper input sanitization on the 'url' parameter and adds output escaping (esc_url, esc_attr, esc_html) in aal_display_clicks(). Also audit and clean any existing malicious entries in the database.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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