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

CVE-2026-57695

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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 Dan Rossiter Document Gallery document-gallery allows Reflected XSS.This issue affects Document Gallery: from n/a through <= 5.1.0.

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 reflected Cross-site Scripting (XSS) vulnerability exists in Dan Rossiter's Document Gallery plugin for WordPress. The plugin fails to properly sanitize user-supplied input before reflecting it back into the generated web page, allowing an attacker to inject malicious JavaScript code that executes in the victim's browser.

MitigationApply the vendor patch or update to Document Gallery version 5.1.1 or later, which properly sanitizes and encodes output to prevent XSS attacks.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Document Gallery plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Document Gallery' by Dan Rossiter, or check the wp-content/plugins/document-gallery directory exists
    Affected if The Document Gallery plugin is not installed or is not active
  2. Check installed Document Gallery version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the Document Gallery plugin name, or check the main plugin file header for the Version field
    Affected if Version cannot be determined or is below 5.1.1
  3. Confirm plugin processes user input
    The plugin inherently processes user-supplied input when displaying document galleries - check if shortcodes like [document-gallery] or gallery blocks are used on any page, which causes the plugin to reflect URL parameters or user input into the page output
    Affected if The plugin is active and renders gallery content using user-supplied parameters or content
  4. Compare version to fixed release
    Compare the installed version found in step 2 against the fixed version 5.1.1 - any version below 5.1.1 is affected by the reflected XSS vulnerability
    Affected if Installed version is below 5.1.1 and the plugin processes user input on the site

A user is affected if the Document Gallery plugin is installed and active, the installed version is below 5.1.1, and the plugin renders gallery content that reflects user-supplied input.

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

Apply the vendor patch or update to Document Gallery version 5.1.1 or later, which properly sanitizes and encodes output to prevent XSS attacks.

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