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

CVE-2026-5361

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-14
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 Envira Gallery Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API in versions up to and including 1.12.4. This is due to insufficient input sanitization in the update_gallery_data() function and improper output escaping in the gallery_init() function. The sanitize_config_values() function only sanitizes the justified_gallery_theme and justified_row_height parameters, but does not sanitize the arrows parameter. When the arrows value is output in the inline JavaScript configuration, it uses esc_attr() which is designed for HTML attribute contexts, not JavaScript contexts, allowing JavaScript expression injection. 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

The Envira Gallery Lite WordPress plugin versions up to 1.12.4 contain a stored XSS vulnerability in the REST API endpoint. The arrows parameter in the sanitize_config_values() function is not sanitized during input, and when output in the gallery_init() function it uses esc_attr() which is insufficient for JavaScript contexts, allowing injection of arbitrary JavaScript expressions.

MitigationUpdate the plugin to a version that properly sanitizes all configuration parameters including arrows, and replace esc_attr() with proper JavaScript context escaping (e.g., json_encode or wp_json_encode) for inline JavaScript values.

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 Envira Gallery Lite plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Envira Gallery Lite' appears in the installed plugins list
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on 'Envira Gallery Lite' to view the plugin details; compare the version number to the affected range (versions up to 1.12.4)
    Affected if The installed version is 1.12.4 or lower
  3. Identify if the REST API is accessible
    Check if the WordPress REST API is enabled (by default it is); the vulnerable endpoint is the Envira Gallery REST API settings endpoint - this can be confirmed by reviewing the plugin files for REST route registration
    Affected if The REST API is enabled and the plugin registers its REST endpoints
  4. Inspect gallery configurations for injected scripts
    Query the WordPress database postmeta table for any envira_gallery meta records containing script tags or suspicious JavaScript in the arrows parameter field; use SQL: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%envira%'
    Affected if Any gallery configuration contains unsanitized JavaScript or script tags in the arrows parameter

A user is affected if they have Envira Gallery Lite version 1.12.4 or lower installed with the REST API enabled, and their galleries contain malicious script injections in the arrows configuration parameter.

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 the plugin to a version that properly sanitizes all configuration parameters including arrows, and replace esc_attr() with proper JavaScript context escaping (e.g., json_encode or wp_json_encode) for inline JavaScript values.

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