dbcve.org
Slideshow GalleryWordPress extension · Tribulant

CVE-2023-28497

HIGH · 8.8 CVSS v3.1 Published 2023-11-12
Fix available
A fix is available. Upgrade to after 1.7.6 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Tribulant Slideshow Gallery LITE plugin <= 1.7.6 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Tribulant Slideshow Gallery LITE WordPress plugin versions 1.7.6 and below allows attackers to induce authenticated administrators to perform unintended actions (such as modifying gallery settings or content) by tricking them into visiting malicious pages.

MitigationUpdate the Tribulant Slideshow Gallery LITE plugin to a version beyond 1.7.6 that includes CSRF protection, or implement anti-CSRF nonce validation on all state-changing plugin actions until the patch is available.

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
Affected:<= 1.7.6

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the installed plugin version
    Access your WordPress admin panel, go to Plugins > Installed Plugins, find 'Tribulant Slideshow Gallery' or 'Slideshow Gallery', and read the version number displayed under the plugin name
    Affected if The version displayed is 1.7.6 or lower
  2. Check the plugin main file header
    If you have file system access, navigate to /wp-content/plugins/slideshow-gallery/ and open the main PHP file (usually slideshow-gallery.php or similar), then look for the 'Version' header comment in the file
    Affected if The Version header shows 1.7.6 or lower
  3. Verify WordPress admin access exists
    Confirm that administrator accounts can access the WordPress dashboard at /wp-admin/
    Affected if Administrator authentication is enabled and accessible - this is required for the CSRF attack to target admins
  4. Identify state-changing plugin actions
    Check the plugin settings pages in the WordPress admin panel under Slideshow Gallery > Settings or similar menu items where galleries can be created, modified, or deleted
    Affected if The plugin is actively installed with gallery management functionality available to administrators

You are affected if the Tribulant Slideshow Gallery LITE plugin is installed at version 1.7.6 or below and administrators can access the WordPress admin panel.

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
Upgrade available Upgrade to a release after 1.7.6
Interim mitigation

Update the Tribulant Slideshow Gallery LITE plugin to a version beyond 1.7.6 that includes CSRF protection, or implement anti-CSRF nonce validation on all state-changing plugin actions until the patch is available.

Recommended fix High confidence

Slideshow Gallery 1.7.7 or later (latest available version)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Slideshow Gallery' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Directory and upload it manually
  6. 6. After updating, verify the plugin is functioning correctly on your site

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

Fix this in Slideshow Gallery Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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