CVE-2026-7330 json
Auto Affiliate Links <= 6.8.8 - Unauthenticated Stored Cross-Site Scripting via 'url' Parameter
published 2026-05-08 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-28540
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- thedark Auto Affiliate Links
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/6c8ed84e-3504-42e3-821d-794198d7adda?source=cve
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/tags/6.8.6/aal_stats.php#L225
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/trunk/aal_stats.php#L225
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/tags/6.8.8/aal_stats.php#L225
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/trunk/aal_stats.php#L304
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/tags/6.8.8/aal_stats.php#L304
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/trunk/aal_stats.php#L278
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/tags/6.8.8/aal_stats.php#L278
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/tags/6.8.6/aal_stats.php#L304
- plugins.trac.wordpress.org /browser/wp-auto-affiliate-links/tags/6.8.6/aal_stats.php#L278
- plugins.trac.wordpress.org /changeset/3519003/wp-auto-affiliate-links/trunk/aal_stats.php
- plugins.trac.wordpress.org /changeset?old_path=%2Fwp-auto-affiliate-links/tags/6.8.8&new_path=%2Fwp-auto-affiliate-links/tags/6.8.8.1
Sources
- CVE List CVE-2026-7330
- NVD CVE-2026-7330
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.