Skip to main content
VulnerabilityPublished

CVE-2026-119211: AAA Autoload Optimizer (WordPress plugin) · Cross-site Scripting

Affects AAA Autoload Optimizer (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.9 Medium.

Data as of 6 Nov 2026, 11:41 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.14.9
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
progressplannerAAA Autoload OptimizerAffected
  • <=1.7.0
Fixed in–

AI-suggested

Users should avoid configuring the Option Tracking setting to 'Legacy' mode to mitigate the risk. Until a patch is available, restrict plugin access to trusted users with higher privileges and monitor for updates from the vendor or plugin maintainers.

Description

The AAA Autoload Optimizer WordPress plugin up to version 1.7.0 contains a stored cross-site scripting (XSS) vulnerability via the 'option_page' parameter. This flaw allows authenticated users with subscriber-level or higher access to inject malicious scripts that execute when other users view the affected pages. Exploitation requires the plugin's Option Tracking setting to be set to 'Legacy' mode. The vulnerability occurs due to insufficient input sanitization and output escaping, and it bypasses WordPress's HTTP 403 response because the vulnerable filter runs before capability checks.

References

Community reviews

Loading reviews…