CVE-2026-42775
Description
Unauthenticated stored cross-site scripting (XSS) in AutomatorWP <= 5.7.2 allows arbitrary script injection on WordPress sites.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Unauthenticated stored cross-site scripting (XSS) in AutomatorWP <= 5.7.2 allows arbitrary script injection on WordPress sites.
Vulnerability
The AutomatorWP plugin for WordPress versions up to and including 5.7.2 contains an unauthenticated stored cross-site scripting (XSS) vulnerability. The flaw resides in insufficient input sanitization and output escaping, allowing injection of arbitrary HTML and JavaScript. No special user role or authentication is required to trigger the vulnerable code path.
Exploitation
An unauthenticated attacker can inject a malicious payload (e.g., JavaScript) through a crafted request. Successful exploitation requires a privileged user—such as an administrator or editor—to subsequently interact with a page that renders the injected payload, for example by clicking a link, visiting a crafted page, or submitting a form. The attacker does not need any prior access or authentication.
Impact
Upon successful execution, the attacker's script runs in the context of the victim's session. This can be used to steal session cookies, perform actions on behalf of the victim, redirect visitors to malicious sites, or inject unauthorized advertisements and other HTML content. The impact is heightened because no authentication is needed to inject the payload, and the plugin is widely deployed.
Mitigation
The vulnerability is fixed in version 5.7.3. Users should update to this version or later immediately. If updating is not possible, Patchstack has issued a mitigation rule that blocks attacks until a patch is applied. Auto-updates can be enabled for vulnerable plugins via Patchstack [1]. No other workarounds have been published at this time.
AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
1- Wordfence Intelligence Weekly WordPress Vulnerability Report (June 1, 2026 to June 7, 2026)Wordfence Blog · Jun 11, 2026