Slideshow SeWordPress extension · Slideshow Se Project
CVE-2024-35778
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in John West Slideshow SE PHP Local File Inclusion.This issue affects Slideshow SE: from n/a through 2.5.17.
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 confidenceA path traversal vulnerability in John West Slideshow SE PHP versions up to 2.5.17 allows attackers to manipulate file path inputs using '..' sequences to access restricted directories and potentially read sensitive local files via local file inclusion (LFI).
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 SeWordPress extension
<= 2.5.17CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 SE PHP is installedLocate the Slideshow SE installation by searching for slideshow-se.php or related files in your web root or application directory. Check for directories containing 'slideshow' and 'john west' in the name.Affected if The Slideshow SE PHP application is found on the server
-
Identify installed versionOpen the main PHP file (such as slideshow-se.php) and look for a version string, or check any version.txt, README, or changelog file in the installation directory.Affected if The version number is 2.5.17 or lower
-
Verify application is web-accessibleConfirm the Slideshow SE scripts are accessible via HTTP/HTTPS through your web server. Try accessing the main script URL in a browser or via curl.Affected if The application is exposed and reachable via web requests
-
Check for file path input parametersReview the application source code for parameters that accept file paths, file names, or include/require statements that use user-supplied input without sanitization.Affected if The application accepts file path parameters in URL requests (such as ?file=, ?path=, or similar)
-
Test for path traversal susceptibilitySend a request with '../' sequences in path parameters (e.g., ?file=../../../../etc/passwd) to see if the application returns content from outside the intended directory.Affected if The application returns files from directories outside its allowed scope
You are affected if Slideshow SE PHP version 2.5.17 or lower is installed and web-accessible, and the application processes file path parameters that could be manipulated with traversal sequences.
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 dataImplement strict input validation and sanitization for all file path parameters, using whitelist approaches or canonicalizing paths before use to prevent directory traversal characters.
Fix this in Slideshow Se
Scoped from the published advisory
- 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-2024-35778 — 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-2024-35778 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