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

CVE-2026-42643

MEDIUM · 5.9 CVSS v3.1 Published 2026-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/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 StellarWP Image Widget image-widget allows Stored XSS.This issue affects Image Widget: from n/a through <= 4.4.11.

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

A Stored XSS vulnerability exists in the StellarWP Image Widget plugin (versions <= 4.4.11) where user-supplied input—likely in image title, alt text, or URL fields—is not properly sanitized before being rendered in web pages, allowing authenticated attackers to inject malicious JavaScript that executes when site administrators or visitors view the affected widget.

MitigationUpdate the Image Widget plugin to the latest version (> 4.4.11) to obtain the patched code. If no update is available, disable the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins. Locate 'Image Widget' by StellarWP (or StellarWP Image Widget) and check the version number displayed. Alternatively, inspect the plugin main file header via file manager or FTP at /wp-content/plugins/image-widget/ and read the 'Version' comment.
    Affected if The displayed version is 4.4.11 or any version number lower than 4.4.11 (e.g., 4.4.10, 4.4.9, etc.)
  2. Confirm the plugin widget is active on the site
    Visit the site frontend or check Appearance > Widgets in WordPress admin. Identify if any Image Widget instances are placed in active widget areas (sidebars, footers, custom widget areas).
    Affected if Any Image Widget instances are actively displaying on the site; the vulnerability only triggers when the widget output is rendered on a page view.
  3. Inspect stored widget data for unsanitized input
    Access the WordPress database via phpMyAdmin or CLI. Query the wp_options table (or custom options table prefix) for records containing widget_image or similar option names. Examine the stored values in fields corresponding to title, alt text, image URL, and link URL for any raw HTML or script tags.
    Affected if The stored widget configuration contains raw, unescaped HTML characters (<, >, script tags) in title, alt text, or URL fields, indicating the input was not sanitized on save.
  4. Review page source for injected script execution
    View the source HTML of a page containing an Image Widget. Search for the widget's rendered output and verify whether content in title/alt/URL fields appears as plain text or as rendered HTML/script. Use browser DevTools > Elements to inspect the specific widget markup.
    Affected if The rendered page shows script tags, event handlers, or other JavaScript executing from widget fields instead of being displayed as encoded text.

You are affected if the Image Widget plugin version is 4.4.11 or lower AND any Image Widget instances with user-supplied content are actively displayed on the site, allowing injected JavaScript to execute in admin or visitor browsers.

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 Image Widget plugin to the latest version (> 4.4.11) to obtain the patched code. If no update is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Latest version of StellarWP Image Widget (plugin version > 4.4.11)

  1. Check the WordPress plugin repository or StellarWP official source for the latest version of the Image Widget plugin
  2. Update the Image Widget plugin to the latest available version (greater than 4.4.11)
  3. Verify the update was applied successfully
  4. Test the image widget functionality to ensure the upgrade did not break existing features
Caveat Review changelog for any breaking changes between your current version and the latest version before upgrading

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