Skip to main content
CVE-2026-119211VulnerabilityPublished

The AAA Autoload Optimizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'option_page'

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-119211· Medium 4.9

Not known to be exploited · CVSS 4.9 Medium.

Data as of 6 Nov 2026, 13:23 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 using the plugin with the Option Tracking setting configured to 'Legacy' mode. Until a fix is available, restrict plugin usage to trusted users only or disable the plugin. Monitor the vendor advisory for official patches or updates addressing this vulnerability.

Description

The AAA Autoload Optimizer WordPress plugin up to version 1.7.0 is vulnerable to stored cross-site scripting (XSS) via the 'option_page' parameter. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. Exploitation requires the plugin's Option Tracking setting to be in 'Legacy' mode. The vulnerability arises from insufficient input sanitization and output escaping, and it bypasses WordPress's HTTP 403 response due to filter execution order.

References

Community reviews

Loading reviews…