CVE-2026-5191
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 · uneditedThe Tiled Gallery Carousel Without JetPack plugin for WordPress is vulnerable to stored cross-site scripting via the 'data-image-title' parameter in all versions up to, and including, 3.1 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 confidenceThe Tiled Gallery Carousel Without JetPack WordPress plugin fails to properly sanitize the 'data-image-title' parameter during input and escape it during output, allowing authenticated users with contributor-level access or higher to inject malicious JavaScript that executes when other users view affected gallery pages.
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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the plugin is installedNavigate to WordPress admin > Plugins and check if 'Tiled Gallery Carousel Without JetPack' is active or installedAffected if The plugin is installed and active
-
Identify the installed plugin versionIn Plugins list, locate the version number under the plugin name, or check the plugin header in /wp-content/plugins/tiled-gallery-carousel-without-jetpack/tiled-gallery-carousel-without-jetpack.phpAffected if The version is unknown, unpatched, or falls within any vulnerable range (if released)
-
Determine if the plugin's gallery feature is in useCheck WordPress pages, posts, or custom post types for any galleries created using the plugin's tiled gallery block or shortcodeAffected if Tiled galleries are published and viewable by other users
-
Inspect the vulnerable parameter handling in plugin codeLocate the file handling gallery image output (typically in includes/ or templates/ folder within the plugin) and search for 'data-image-title' or similar image title attribute output; verify if esc_attr() is applied to this valueAffected if The code outputs data-image-title without esc_attr() or uses the raw unsanitized title value
-
Review user accounts with contributor-level accessIn WordPress admin > Users, list accounts with Contributor, Author, Editor, or Administrator roles who can create or edit gallery contentAffected if There are users with contributor-level or higher permissions who could potentially inject malicious script
A user is affected if the plugin is installed, uses the tiled gallery feature, and the data-image-title parameter is output without proper escaping in the plugin code.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to version 3.2 or later which includes proper sanitization of the data-image-title parameter and output escaping. If no update is available, implement Web Application Firewall rules to detect and block XSS payloads in this parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5191 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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