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

CVE-2026-4766

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-25
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 Easy Image Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Gallery shortcode post meta field in all versions up to, and including, 1.5.3. This is due to insufficient input sanitization and output escaping on user-supplied gallery shortcode values. 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.

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

The Easy Image Gallery WordPress plugin up to version 1.5.3 contains a stored XSS vulnerability in the Gallery shortcode post meta field. Due to insufficient input sanitization and output escaping on user-supplied gallery shortcode values, authenticated attackers with Contributor-level access or higher can inject arbitrary JavaScript that executes whenever users view injected pages.

MitigationUpdate the plugin to a version beyond 1.5.3 once patched, or implement proper input sanitization (e.g., sanitize_text_field, esc_attr) and output escaping (e.g., esc_html, esc_js) on all gallery shortcode values before rendering in the plugin code.

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. Verify Easy Image Gallery plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Image Gallery' in the list. Note the installed version number displayed below the plugin name.
    Affected if Plugin is installed and version is 1.5.3 or earlier (versions through 1.5.3 are affected)
  2. Check WordPress database for plugin version
    Query the wp_options table: SELECT option_value FROM wp_options WHERE option_name = 'easy_image_gallery_version'; OR query wp_posts for posts using the gallery shortcode: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[easy_image_gallery%' AND post_status != 'trash';
    Affected if Plugin version returned is 1.5.3 or lower, OR posts containing the [easy_image_gallery] shortcode exist in the database
  3. Inspect gallery shortcode post meta values
    Query the wp_postmeta table for meta_key containing 'gallery_shortcode' or similar: SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE meta_key LIKE '%gallery%shortcode%' OR meta_key LIKE '%easy_image%'; Manually review the meta_value field for any unsanitized HTML or script tags.
    Affected if Post meta contains raw HTML, script tags, or JavaScript event handlers (onclick, onerror, etc.) without proper escaping
  4. Check for stored XSS in gallery image IDs field
    Examine the post meta where meta_key is 'gallery_shortcode' or 'easy_image_gallery' - look at the stored value format. If it contains unescaped quotes, <script> tags, or javascript: URIs, the vulnerability is present.
    Affected if Meta values contain unescaped special characters, raw HTML tags, or javascript: protocol handlers in the shortcode parameters

Your environment is affected if the Easy Image Gallery plugin version is 1.5.3 or earlier AND any posts/pages contain gallery shortcode values that have not been sanitized (containing raw HTML, script tags, or javascript: handlers in the post meta).

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 1.5.3 once patched, or implement proper input sanitization (e.g., sanitize_text_field, esc_attr) and output escaping (e.g., esc_html, esc_js) on all gallery shortcode values before rendering in the plugin code.

Recommended fix Moderate confidence

Version 1.5.4 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Easy Image Gallery plugin
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/easy-image-gallery/ and upload via Plugins > Add New > Upload Plugin
  6. Verify the update was successful by checking the plugin version is 1.5.4 or higher
  7. Test that existing galleries still function correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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