Slideshow GalleryWordPress extension · Tribulant
CVE-2023-28491
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Tribulant Slideshow Gallery LITE.This issue affects Slideshow Gallery LITE: from n/a through 1.7.6.
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 confidenceSQL injection vulnerability in Tribulant Slideshow Gallery LITE plugin allows attackers to inject malicious SQL queries through unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or data manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Slideshow GalleryWordPress extension
<= 1.7.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 Slideshow Gallery plugin is installedNavigate to WordPress admin plugins page and locate 'Slideshow Gallery' or 'Tribulant Slideshow Gallery' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Identify installed plugin versionClick on the plugin in the WordPress plugins list to view details, or inspect the main plugin file (usually slideshow-gallery.php) and look for a 'Version' header in the plugin commentsAffected if Version number is 1.7.6 or lower
-
Verify plugin is activeCheck the plugins list status - the plugin must be activated for the vulnerability to be exploitableAffected if Plugin status shows as 'Active'
-
Confirm plugin is accessible to usersTest whether the gallery functionality is accessible to unauthenticated visitors or low-privilege users on the site frontendAffected if Gallery shortcodes or endpoints are publicly accessible without authentication
-
Inspect plugin for vulnerable SQL patternsExamine PHP files in the plugin directory, particularly files handling gallery queries, for direct use of $_GET, $_POST, or $_REQUEST in SQL queries without prepare() or esc_sql() functionsAffected if Unsanitized user input is used in SQL queries (e.g., 'SELECT * FROM ... WHERE id = ' . $_GET['id'] without prepared statements)
Environment is affected if Slideshow Gallery LITE plugin version 1.7.6 or lower is installed and active, with the vulnerable SQL query code accessible to unauthenticated users.
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 Slideshow Gallery LITE to the latest version beyond 1.7.6, or implement parameterized queries/ prepared statements to sanitize input in the affected SQL queries.
Fix this in Slideshow Gallery
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28491 — 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-2023-28491 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