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

CVE-2026-39665

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Vladimir Prelovac SEO Friendly Images seo-image allows DOM-Based XSS.This issue affects SEO Friendly Images: from n/a through <= 3.0.5.

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 · moderate confidence

DOM-based Cross-site Scripting (XSS) vulnerability in the SEO Friendly Images WordPress plugin (seo-image) allows attackers to inject malicious JavaScript through unsanitized input that gets rendered in the browser's DOM without proper output encoding.

MitigationUpdate SEO Friendly Images plugin to the latest version which includes proper input sanitization and output encoding for all user-controlled data rendered in the browser.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 SEO Friendly Images plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'SEO Friendly Images' in the list. Note whether it is active or inactive.
    Affected if Plugin is installed and active - inactive plugins do not expose the vulnerability
  2. Check the installed version number
    In the plugins list, click on the plugin name or view details to see the version number displayed. Compare this against version 3.0.5.
    Affected if Version is 3.0.5 or any lower version number
  3. Identify plugin settings configuration
    Navigate to Settings > SEO Friendly Images in the WordPress admin panel. Review what fields accept user input, such as alt text templates or title templates for images.
    Affected if Plugin settings contain customizable templates that accept user-supplied values for image attributes
  4. Confirm DOM rendering of image attributes
    View the HTML source of a page on the site that contains images processed by the plugin. Look for img tags with alt and title attributes that reflect values from the plugin settings.
    Affected if Image tags on the frontend contain alt or title attributes populated from plugin settings - the vulnerability lies in how these are rendered in the browser's DOM

The environment is affected if the SEO Friendly Images plugin is active, installed version is 3.0.5 or lower, and the plugin is configured to output image alt text or title attributes on the frontend.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update SEO Friendly Images plugin to the latest version which includes proper input sanitization and output encoding for all user-controlled data rendered in the browser.

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-39665 — 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-39665 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