dbcve.org
Slideshow GalleryWordPress extension · Tribulant

CVE-2024-31353

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 1.7.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Insertion of Sensitive Information into Log File vulnerability in Tribulant Slideshow Gallery.This issue affects Slideshow Gallery: from n/a through 1.7.8.

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

The Slideshow Gallery WordPress plugin (versions through 1.7.8) contains a vulnerability where sensitive information is being written to log files. This type of CWE-532 vulnerability allows unauthorized actors to potentially access sensitive data (such as credentials, session tokens, or user data) by reading application logs if they have file system access or if logs are exposed via web server misconfiguration.

MitigationIdentify and remediate the code paths writing sensitive data to logs; ensure logs are stored outside the web root with restricted permissions; consider implementing log sanitization or masking of sensitive fields before logging.

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.8

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm Slideshow Gallery plugin is installed
    Navigate to WordPress admin Dashboard > Plugins > Installed Plugins and look for 'Slideshow Gallery' by Tribulant, or check the file system at wp-content/plugins/slideshow-gallery/ for the plugin directory
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Open wp-content/plugins/slideshow-gallery/readme.txt and locate the 'Stable tag' entry, or check the plugin header comment in the main PHP file for the 'Version' field
    Affected if The version is less than 1.7.8 (any version through 1.7.8 is affected)
  3. Locate plugin-related log files
    Search for log files in the plugin directory (wp-content/plugins/slideshow-gallery/), the WordPress root, wp-content/, or common log directories. Look for files with .log, .txt, or debug extensions that may contain 'slideshow' or 'gallery' in the name
    Affected if Log files exist in accessible locations
  4. Inspect log files for sensitive data
    Open any found log files and search for patterns indicating sensitive information: password=, pwd, token, session, Authorization, API key, secret, user_email, or SQL queries containing user data
    Affected if Log files contain credentials, session tokens, API keys, user data, or other sensitive fields
  5. Check file permissions on log files
    Use 'ls -la' on discovered log files to verify if permissions allow unintended access (world-readable, group-readable by non-admin users)
    Affected if Log files have overly permissive access controls

A user is affected if the Slideshow Gallery plugin version is below 1.7.8 AND log files exist containing unsanitized sensitive data accessible to unauthorized users.

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 1.7.8 or later
Fixed in 1.7.8
Interim mitigation

Identify and remediate the code paths writing sensitive data to logs; ensure logs are stored outside the web root with restricted permissions; consider implementing log sanitization or masking of sensitive fields before logging.

Recommended fix Moderate confidence

Slideshow Gallery version 1.7.8

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate the Slideshow Gallery plugin by Tribulant
  4. Check the current installed version to confirm it is below 1.7.8
  5. Update the plugin to version 1.7.8 or latest available version
  6. Verify the update was successful and the plugin is functioning correctly
  7. Test the slideshow functionality to ensure no breaking changes

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

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-2024-31353 — 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-2024-31353 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