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

CVE-2026-3722 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%.

Auto Image Attributes CVE-2026-3722

EUVD-2026-33869 MEDIUM

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

2026-06-02 Wordfence

GHSA-v3r3-x7w3-4wc7

WordPress XSS Wordpress Plugin Auto Image Attributes From Filename With Bulk Updater Add Alt Text Image Title For Image Seo

6.4

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

6.4 MEDIUM

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

Primary rating from Vendor (Wordfence) · only source for this CVE.

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 02, 2026 - 02:45 vuln.today

CVE Published

Jun 02, 2026 - 01:28 nvd

MEDIUM 6.4

DescriptionCVE.org

The Auto Image Attributes From Filename With Bulk Updater (Add Alt Text, Image Title For Image SEO) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the attachment metadata in all versions up to, and including, 4.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AnalysisAI

Stored Cross-Site Scripting in the Auto Image Attributes From Filename With Bulk Updater WordPress plugin (all versions through 4.9) allows authenticated attackers holding Author-level access or higher to persist arbitrary JavaScript payloads via unsanitized attachment metadata fields. The injected scripts execute in the browser of any user who subsequently accesses the affected page, with Changed scope (S:C) indicating the payload crosses the plugin's trust boundary into the broader WordPress session context. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.

Technical ContextAI

The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS). The plugin processes image attachment metadata (such as filename-derived alt text and title values) without adequate input sanitization before storage and without proper output escaping before rendering. Based on the Wordfence source code references, the two vulnerable locations are admin/columns-media-library.php at line 50 (likely the media library column renderer) and admin/do.php at line 752 (likely the bulk updater processing routine). The CPE string cpe:2.3:a:arunbasillal:auto_image_attributes_from_filename_with_bulk_updater_(...):*:*:*:*:*:*:*:* confirms the vendor is arunbasillal and the affected product scope covers all prior version strings up through 4.9. Because WordPress plugins render output within the WordPress admin and front-end page contexts, a stored XSS payload in attachment metadata propagates to every page or admin view that displays that attachment's attributes.

RemediationAI

No vendor-released patch version has been independently confirmed from the available input data; the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/9696fae6-39fe-4478-90e7-488b5b573fa8?source=cve should be checked for an updated plugin version above 4.9. If a patched release is not yet available, the most actionable compensating control is to restrict Author-level role assignment - audit WordPress user roles and reduce Author accounts to the minimum necessary set, as this directly eliminates the required privilege level (PR:L). As an additional control, WordPress site administrators can disable the plugin entirely until a patch is confirmed, accepting the loss of automated alt-text and image title generation. Web Application Firewall (WAF) rules targeting stored XSS payloads in media upload requests (such as those offered by Wordfence Premium) can provide partial mitigation but should not substitute for patching, as WAF bypass techniques exist. Restricting media uploads to trusted roles only (e.g., Editor and above rather than Author) also reduces attack surface without disabling the plugin entirely.