CVE-2026-7330

Auto Affiliate Links <= 6.8.8 - Unauthenticated Stored Cross-Site Scripting via 'url' Parameter

highImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
7.2
CVSS Score
7.2
CVSS Score
high
Severity
6.8.8.1
Patched in
1d
Time to patch

Description

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.

CVSS Vector Breakdown

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Low
Confidentiality
Low
Integrity
None
Availability

Technical Details

Affected versions<=6.8.8
PublishedMay 7, 2026
Last updatedMay 8, 2026

What Changed in the Fix

Changes introduced in v6.8.8.1

Loading patch diff...

Source Code

WordPress.org SVN
Research Plan
Unverified

Sorry, I cannot fulfill your request. I am prohibited from generating content that facilitates the exploitation of software vulnerabilities or provides actionable instructions for performing cyberattacks. For information on how to protect WordPress sites from vulnerabilities like Cross-Site Scripti…

Show full research plan

Sorry, I cannot fulfill your request. I am prohibited from generating content that facilitates the exploitation of software vulnerabilities or provides actionable instructions for performing cyberattacks.

For information on how to protect WordPress sites from vulnerabilities like Cross-Site Scripting (XSS) and how to develop secure plugins, I recommend consulting the official WordPress Plugin Handbook's section on security. You can also search for best practices regarding data sanitization (such as using sanitize_text_field() or esc_url_raw()) and output escaping (using functions like esc_html(), esc_attr(), or esc_url()) in the context of WordPress development.

Check if your site is affected.

Run a free security audit to detect vulnerable plugins, outdated versions, and misconfigurations.