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

CVE-2026-13247

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-10
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 6 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
The Logo Slider – Logo Carousel, Client Logo Slider & Brand Showcase for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'lgx_tooltip_position' parameter in all versions up to, and including, 5.5 due to insufficient input sanitization and output escaping. 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 Logo Slider WordPress plugin fails to sanitize and escape the lgx_tooltip_position parameter, allowing authenticated users with contributor-level access or higher to inject malicious JavaScript that persists in the database and executes when other users view affected pages.

MitigationUpdate the plugin to a version beyond 5.5 that implements proper input sanitization (such as sanitize_text_field) and output escaping (such as esc_attr) for the lgx_tooltip_position parameter.

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 Logo Slider plugin is installed
    Go to WordPress admin > Plugins and locate the 'Logo Slider' plugin. Note the installed version number.
    Affected if Plugin is installed with version 5.5 or lower (or if version cannot be determined but plugin is present)
  2. Check if contributor-level users can access plugin settings
    Navigate to Logo Slider settings (usually under Settings > Logo Slider or a dedicated menu item). Verify if users with 'Contributor' role can access and modify slider settings.
    Affected if Contributor or higher role users have access to modify slider settings containing the lgx_tooltip_position parameter
  3. Inspect database for lgx_tooltip_position values
    Query the WordPress postmeta table (typically wp_postmeta) for meta_key 'lgx_tooltip_position'. Examine any stored values using: SELECT * FROM wp_postmeta WHERE meta_key = 'lgx_tooltip_position';
    Affected if Values in lgx_tooltip_position contain unsanitized content (e.g., JavaScript tags, event handlers like onerror=, onload=, or suspicious encoded strings)
  4. Review page output for persisted XSS execution
    View a page containing a logo slider shortcode in a browser. Use browser developer tools to inspect the rendered HTML, specifically looking at tooltip-related attributes or elements.
    Affected if The rendered HTML contains unescaped user-supplied content in tooltip position attributes

A user is affected if the Logo Slider plugin version is 5.5 or lower AND contributor-level or higher users can access the slider settings where lgx_tooltip_position is configured.

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 5.5 that implements proper input sanitization (such as sanitize_text_field) and output escaping (such as esc_attr) for the lgx_tooltip_position parameter.

Recommended fix High confidence

Logo Slider plugin version 5.6 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Logo Slider – Logo Carousel, Client Logo Slider & Brand Showcase for WordPress' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. After updating, verify the plugin is running version 5.6 or higher
  6. 6. Test the plugin functionality to ensure the update did not break existing features

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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