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

CVE-2026-1913

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-22
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 Gallagher Website Design plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's login_link shortcode in all versions up to, and including, 2.6.4 due to insufficient input sanitization and output escaping on the 'prefix' attribute. 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 Gallagher Website Design WordPress plugin before version 2.6.5 contains a stored XSS vulnerability in the login_link shortcode's 'prefix' attribute. Authenticated users with Contributor-level access can inject malicious JavaScript through insufficiently sanitized input, which executes when other users view affected pages.

MitigationUpdate the plugin to version 2.6.5 or later, which includes proper sanitization of the prefix attribute and output escaping. Until then, restrict contributor-level user creation and audit existing content for malicious shortcode usage.

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 plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Gallagher Website Design' or check the plugin header files for the Version field
    Affected if The plugin is installed and the version is lower than 2.6.5 (or version cannot be determined)
  2. Identify Contributor-level users
    Navigate to Users > All Users in WordPress admin and review the role column for users with Contributor role
    Affected if Any Contributor-level user accounts exist in the WordPress installation
  3. Search for login_link shortcode usage
    Query the WordPress database (wp_posts table) or use a plugin to search post content for the string '[login_link' to find pages using this shortcode
    Affected if Pages or posts contain the login_link shortcode
  4. Inspect prefix attribute values in shortcodes
    Review the shortcode usage found in the previous step, specifically looking for any 'prefix=' attributes and their values
    Affected if The login_link shortcode is used with a prefix attribute that contains special characters (< > " ' or JavaScript)
  5. Check for unescaped output in rendered pages
    View a page containing the login_link shortcode as a different user (or in a browser) and inspect the page source around the login link area
    Affected if The prefix value renders as raw HTML or JavaScript rather than being escaped

The environment is affected if the Gallagher Website Design plugin version is below 2.6.5 AND the login_link shortcode with a prefix attribute is in use, especially with untrusted Contributor-level authors.

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 version 2.6.5 or later, which includes proper sanitization of the prefix attribute and output escaping. Until then, restrict contributor-level user creation and audit existing content for malicious shortcode usage.

Recommended fix High confidence

Version 2.6.5 or later (check WordPress plugin repository for latest release)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'Gallagher Website Design' plugin in the list.
  4. 4. Check the current version installed (displayed under the plugin name).
  5. 5. If the installed version is 2.6.4 or below, update the plugin to the latest available version.
  6. 6. To update: click 'Update Now' if an update is available, or manually download the latest version from the WordPress plugin repository and upload it.
  7. 7. After updating, verify the fix by confirming the plugin version is above 2.6.4.
  8. 8. Test the login_link shortcode to ensure it functions correctly with the prefix attribute.

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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