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

CVE-2026-42688

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
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
Subscriber Cross Site Scripting (XSS) in Modula Image Gallery <= 2.14.23 versions.

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 Modula Image Gallery WordPress plugin versions 2.14.23 and below contains a stored Cross-Site Scripting (XSS) vulnerability that can be exploited by users with subscriber-level privileges, allowing injection of malicious scripts through the plugin's gallery functionality.

MitigationUpdate Modula Image Gallery to a version newer than 2.14.23, or disable/remove the plugin if no patched version is available.

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. Confirm Modula Image Gallery is installed
    Navigate to WordPress admin dashboard > Plugins, or check the file system at wp-content/plugins/ for a folder named 'modula-image-gallery' or similar
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the Modula Image Gallery entry to read the version number, or open the main plugin PHP file (e.g., modula.php) and look for a Version: header in the plugin comments
    Affected if Version displayed is 2.14.23 or lower
  3. Verify subscriber-level access exists
    In WordPress admin, go to Users > All Users and check if any users with the 'Subscriber' role exist, or inspect user capabilities in the wp_users and wp_usermeta tables
    Affected if Subscriber accounts are present in the system
  4. Inspect gallery configurations for injected scripts
    Access the Modula Image Gallery settings or individual gallery configurations (typically found under 'Modula' in the admin sidebar), and examine gallery title, description, image captions, or link fields for suspicious script tags or event handlers
    Affected if Any gallery contains unexpected <script> tags, javascript: URIs, or event handlers like onload, onerror, onclick in gallery fields

A user is affected if the Modula Image Gallery plugin is installed with version 2.14.23 or lower AND subscriber-level accounts can access the gallery creation/editing functionality, or if existing galleries contain injected malicious scripts.

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 Modula Image Gallery to a version newer than 2.14.23, or disable/remove the plugin if no patched version is available.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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