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

CVE-2026-3722

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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
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.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in a WordPress image SEO plugin. The plugin fails to properly sanitize attachment metadata fields (such as alt text and image titles) when input is received, and fails to escape this data when outputting it to pages. An authenticated attacker with Author-level access or higher can inject malicious JavaScript into image metadata that will execute whenever users view pages containing the injected image.

MitigationUpdate the plugin to a version beyond 4.9 if available, or implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_attr) and output escaping (esc_html, esc_attr) on all attachment metadata fields before rendering.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins. Locate 'Auto Image Attributes' (may also be named 'Auto Image Attributes with Bulk SEO') and note the version number displayed. Compare this against version 4.10 and later.
    Affected if The installed version is below 4.10 (e.g., 4.9.x, 4.8.x, etc.)
  2. Verify plugin is active
    In the Plugins list, check if Auto Image Attributes shows as 'Active' under the plugin status column.
    Affected if The plugin is active and the version is below 4.10
  3. Check for Author-level or higher users
    Go to WordPress admin > Users. Review the user list to identify any accounts with the role of Author, Editor, or Administrator.
    Affected if The site has users with Author-level or higher privileges, which is required to exploit this vulnerability
  4. Inspect image metadata for injection attempts
    Access the WordPress Media Library. Click on several images and review the 'Alt Text' and 'Title' fields in the attachment details panel. Look for unexpected characters, script tags, or encoded payloads.
    Affected if Any image entries contain unsanitized JavaScript payloads in alt text or title fields

A site is affected if the Auto Image Attributes plugin is installed, active, and running a version prior to 4.10, and the site has users with Author-level permissions or higher who could have injected malicious metadata.

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 the plugin to a version beyond 4.9 if available, or implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_attr) and output escaping (esc_html, esc_attr) on all attachment metadata fields before rendering.

Recommended fix Moderate confidence

A version newer than 4.9 (check WordPress plugin repository for the latest release)

  1. 1. Log in to the WordPress admin dashboard with an administrator account
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Auto Image Attributes From Filename With Bulk Updater' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is newer than 4.9
  6. 6. Test image upload functionality to ensure the plugin still works correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3722 — 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-3722 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