CVE-2026-56045

WordPress Automatic Plugin < 3.135.1 - Unauthenticated Stored Cross-Site Scripting

2026-06-25 00:00
Nguyen Ba Khanh

Strategic Overview

Status
Patched in 3.135.1
Affected Plugin
WordPress Automatic Plugin
Affected Version
< 3.135.1
CVSS
7.2High
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2026-56045
View all WordPress Automatic Plugin vulnerabilities

At a glance

CVE-2026-56045 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WordPress Automatic Plugin WordPress plugin, affecting versions < 3.135.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.135.1; sites on affected versions should update now. Disclosed June 2026, reported by Nguyen Ba Khanh.

Vulnerability Overview

The WordPress Automatic Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to 3.135.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WordPress Automatic Plugin < 3.135.1 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WordPress Automatic Plugin the fix is 3.135.1: builds < 3.135.1 are affected, anything from 3.135.1 onward is not.

Remediation

Update to version 3.135.1, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WordPress Automatic Plugin 3.135.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-56045https://www.wordfence.com/threat-intel/vulnerabilities/id/045f52f2-b77d-4ddb-a674-0fccf3e6dc7dhttps://nvd.nist.gov/vuln/detail/CVE-2026-56045

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C