What is the CVSS score of CVE-2026-2430?

CVE-2026-2430 has a CVSS 3.1 base score of 6.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of WordPress are affected by CVE-2026-2430?

Organizations using Autoptimize should be aware of moderate risk from CVE-2026-2430, a cross-site scripting vulnerability rated CVSS 6.4.

How to fix or mitigate CVE-2026-2430?

Within 30 days: Identify affected systems running for WordPress is vulnerable to Stored Cross-Site Scripting v and apply vendor patches as part of regular patch cycle. Verify Content-Security-Policy and output encoding.

WordPress CVE-2026-2430

EUVD-2026-13842 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-03-20 Wordfence

WordPress XSS

6.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.4 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 20, 2026 - 23:46 euvd

EUVD-2026-13842

Analysis Generated

Mar 20, 2026 - 23:46 vuln.today

CVE Published

Mar 20, 2026 - 23:25 nvd

MEDIUM 6.4

DescriptionCVE.org

The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the lazy-loading image processing in all versions up to, and including, 3.1.14. This is due to the use of an overly permissive regular expression in the add_lazyload function that replaces all occurrences of \ssrc= in image tags without limiting to the actual attribute. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page by crafting an image tag where the src URL contains a space followed by src=, causing the regex to break the HTML structure and promote text inside attribute values into executable HTML attributes.

AnalysisAI

The Autoptimize WordPress plugin contains a Stored Cross-Site Scripting (XSS) vulnerability in the lazy-loading image processing function that allows authenticated attackers with Contributor-level access to inject arbitrary web scripts into pages. The flaw exists in all versions up to and including 3.1.14 and stems from an overly permissive regular expression that fails to properly validate image tag attributes, enabling attackers to craft malicious image tags that break HTML structure and promote attribute values into executable code. This vulnerability carries a moderate CVSS score of 6.4 and requires user interaction for stored XSS payloads to execute when pages are accessed.

Technical ContextAI

The vulnerability resides in the add_lazyload function within the Autoptimize plugin (CPE: cpe:2.3:a:optimizingmatters:autoptimize:*:*:*:*:*:*:*:*), specifically in the autoptimizeImages.php class file. The root cause is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation, or Cross-site Scripting). The vulnerable code uses a naive regular expression pattern matching \ssrc= (a space followed by 'src=') to process image tags for lazy-loading functionality. This regex-based string replacement approach fails to distinguish between legitimate src attributes within img tags and malicious src sequences injected elsewhere in the HTML, such as within other attribute values or as part of URL parameters. When an attacker crafts an image tag with a src URL containing a space followed by 'src=', the regex matches unintended occurrences and breaks the HTML structure, effectively promoting text that should remain in attribute values into executable HTML attributes where inline event handlers or protocol handlers can be injected.

RemediationAI

Immediately upgrade Autoptimize to a version released after 3.1.14, which includes the fix committed to the GitHub repository (https://github.com/futtta/autoptimize/commit/a0f87112fe80b5a97b036229c41cb18454392858). In WordPress admin, navigate to Plugins, find Autoptimize, and click Update. As an interim measure for organizations unable to patch immediately, restrict Contributor-level access to only trusted users, audit existing contributors for compromise, and review page content and post revisions for suspicious image tags containing space-separated src attributes. Consider implementing a Web Application Firewall (WAF) rule to detect and block HTTP requests containing image tags with the malicious pattern (space followed by src= in URL parameters or post content). Monitor WordPress audit logs for posts created or modified by lower-privileged users during the vulnerability window to identify potential exploitation attempts.