dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-42650

HIGH · 7.2 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthenticated Cross Site Scripting (XSS) in AutomatorWP <= 5.6.7 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated Cross-Site Scripting (XSS) vulnerability in AutomatorWP plugin for WordPress versions 5.6.7 and below allows remote attackers to inject malicious JavaScript scripts through unsanitized input fields.

MitigationUpdate AutomatorWP to the latest version available (newer than 5.6.7) to patch the XSS vulnerability. Additionally, implement WAF rules as a temporary measure if immediate update is not possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AutomatorWP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for AutomatorWP in the list. Alternatively, check the /wp-content/plugins/automatorwp/ directory exists on the server.
    Affected if AutomatorWP plugin is present on the WordPress site
  2. Determine installed AutomatorWP version
    In WordPress admin, go to Plugins > Installed Plugins and click on AutomatorWP to view the version number. Alternatively, check the main plugin file (automatorwp.php) for the 'Version' header comment.
    Affected if Installed version is 5.6.7 or lower
  3. Confirm XSS input vectors are accessible
    The vulnerability affects unsanitized input fields accessible to unauthenticated users. Review AutomatorWP automation triggers and form submissions that accept user input without authentication requirements.
    Affected if Unauthenticated users can submit data through AutomatorWP forms or triggers
  4. Compare version to affected range
    Cross-reference the installed version against the affected range: versions 5.6.7 and below are vulnerable. Any version older than 5.6.7 is affected.
    Affected if Installed version is 5.6.7 or any earlier version of AutomatorWP

If AutomatorWP plugin is installed and the version is 5.6.7 or below, the site is affected by this unauthenticated XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update AutomatorWP to the latest version available (newer than 5.6.7) to patch the XSS vulnerability. Additionally, implement WAF rules as a temporary measure if immediate update is not possible.

Recommended fix Moderate confidence

Latest available version of AutomatorWP (newer than 5.6.7)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Find AutomatorWP plugin and check if current version is 5.6.7 or lower
  4. 4. If vulnerable, click 'Update Now' to install the latest version, or manually download the latest version from wordpress.org/plugins/automatorwp/
  5. 5. After updating, verify the plugin version shows a version newer than 5.6.7
  6. 6. Test critical automation workflows to ensure functionality is intact
Caveat Minor or no breaking changes expected for security patch updates; test automation workflows after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42650 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data