CVE-2026-119211: AAA Autoload Optimizer <= 1.7.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'option_page' Parameter via 'all' Hook

Q: Which sites are exposed to exploitation?

Sites running AAA Autoload Optimizer version 1.7.0 or earlier are exposed only when its Option Tracking setting is configured to Legacy mode. The attacker must also have an authenticated WordPress account with at least Subscriber-level access.

Q: Does the HTTP 403 response prevent exploitation by low-privileged users?

No. The vulnerable all filter runs before the capability check in wp-admin/options.php, so script injection can succeed even though WordPress ultimately returns HTTP 403 to the low-privileged caller.

Q: What is the impact of successful exploitation?

An authenticated low-privileged attacker can store arbitrary web scripts in an injected page. Those scripts execute when a user accesses that page, potentially affecting users with greater privileges.

Published Nov 6, 2026

Updated

The AAA Autoload Optimizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'optionpage' parameter in all versions up to, and including, 1.7.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the plugin's Option Tracking setting to be configured to 'Legacy' mode, and succeeds despite WordPress ultimately returning HTTP 403 to the low-privileged caller because the vulnerable 'all' filter fires before the capability check in wp-admin/options.php.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Configuration
Change the Option Tracking setting from 'Legacy' mode to a non-Legacy mode to prevent exploitation of the vulnerable path.
AAA Autoload Optimizer Option Tracking = non-Legacy mode

Event History

Nov 6, 2026

CVE Published

via MITRE·11:17 AM

Data Sourced

via MITRE·11:17 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Which sites are exposed to exploitation?

Sites running AAA Autoload Optimizer version 1.7.0 or earlier are exposed only when its Option Tracking setting is configured to Legacy mode. The attacker must also have an authenticated WordPress account with at least Subscriber-level access.

Does the HTTP 403 response prevent exploitation by low-privileged users?

No. The vulnerable all filter runs before the capability check in wp-admin/options.php, so script injection can succeed even though WordPress ultimately returns HTTP 403 to the low-privileged caller.

What is the impact of successful exploitation?

An authenticated low-privileged attacker can store arbitrary web scripts in an injected page. Those scripts execute when a user accesses that page, potentially affecting users with greater privileges.

CVE-2026-119211: AAA Autoload Optimizer <= 1.7.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'option_page' Parameter via 'all' Hook

Remediation

Event History

Frequently Asked Questions

Which sites are exposed to exploitation?

Does the HTTP 403 response prevent exploitation by low-privileged users?

What is the impact of successful exploitation?

Company

Resources

Contact

Frequently Asked Questions

Which sites are exposed to exploitation?

Does the HTTP 403 response prevent exploitation by low-privileged users?

What is the impact of successful exploitation?