---
id: "CVE-2026-119211"
page: "https://infrastack.ai/live/CVE-2026-119211"
kind: "vulnerability"
aliases: ["CVE-2026-119211"]
title: "WordPress AAA Autoload Optimizer: stored script injection via option_page parameter"
severity: "medium"
cvss: 4.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "wordpress", "wordpress-plugins"]
not_affected_if: ["auth-required", "option-tracking-not-legacy", "plugin-not-installed"]
published_at: "2026-11-06T12:17:19+00:00"
first_seen_at: "2026-11-06T12:41:48+00:00"
updated_at: "2026-11-06T12:42:56+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119211", "first_seen_at": "2026-11-06T12:41:48+00:00"}]
exploit_sources: []
---

# WordPress AAA Autoload Optimizer: stored script injection via option_page parameter

Link for people: https://infrastack.ai/live/CVE-2026-119211 (this .md is for agents)

The AAA Autoload Optimizer plugin for WordPress fails to sanitize the 'option_page' parameter, so a logged-in subscriber can store a script that runs in the browser of any user who opens the injected page. Exploitation needs the plugin's Option Tracking setting set to 'Legacy' mode.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of the AAA Autoload Optimizer plugin; versions up to and including `1.7.0` are affected.
- In the plugin's settings, check whether Option Tracking is set to 'Legacy'.

## Timeline

- 2026-11-06T12:41:48+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119211

## From the sources

The AAA Autoload Optimizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'option_page' 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_