dbcve.org
StrikingWordPress extension · Kaptinlin

CVE-2024-37268

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 2.3.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in kaptinlin Striking allows Path Traversal.This issue affects Striking: from n/a through 2.3.4.

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

Path Traversal vulnerability in the Striking WordPress theme allows attackers to access files outside the web root directory due to improper validation of user-supplied file paths, potentially exposing sensitive system files.

MitigationImplement strict path validation and sanitization to ensure all file paths remain within the intended directory. Use realpath() to resolve and validate paths, and whitelist allowed file access patterns.

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
StrikingWordPress extension
Affected:< 2.3.5

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
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 checks

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

  1. Confirm Striking theme is installed
    Navigate to wp-content/themes/ or check WordPress admin Appearance > Themes to list installed themes. Look for a theme folder named 'Striking' or 'kaptinlin'
    Affected if The Striking theme by Kaptinlin is present in the WordPress installation
  2. Identify the theme version
    Open the style.css file in the Striking theme folder (wp-content/themes/striking/style.css) and locate the 'Version:' header in the file comments
    Affected if The version number found is lower than 2.3.5 (e.g., 2.3.4, 2.3.0, etc.)
  3. Locate vulnerable file handling code
    Search the theme folder for PHP files that handle file operations (download, include, require, file_get_contents) with user-supplied paths. Common filenames include download.php, file.php, or similar. Inspect these files for path parameters used without realpath() validation
    Affected if File handling scripts exist that accept path parameters without proper path validation
  4. Check for unrestricted path traversal capability
    In identified file handling scripts, verify whether the code uses functions like realpath(), basename(), or whitelist validation before accessing files. Look for patterns like '$_GET[path]' or '$_POST[file]' used directly in file operations
    Affected if The code accepts user-supplied paths and uses them directly in file operations without realpath() or whitelist validation
  5. Review access logs for exploitation attempts
    Check web server access logs (Apache error.log, access.log or Nginx access.log) for requests to the theme's file handling scripts with '../' sequences or absolute path attempts (e.g., /etc/passwd, ../../windows)
    Affected if Log entries show requests containing '../' patterns or attempts to access system files through theme file handlers

The environment is affected if the Striking theme version is below 2.3.5 AND file handling functionality exists that accepts unsanitized path parameters from 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 2.3.5 or later
Fixed in 2.3.5
Interim mitigation

Implement strict path validation and sanitization to ensure all file paths remain within the intended directory. Use realpath() to resolve and validate paths, and whitelist allowed file access patterns.

Recommended fix High confidence

Striking version 2.3.5

  1. Back up your current website files and database before making any changes
  2. Navigate to your WordPress dashboard and go to Appearance > Themes
  3. Locate the Striking theme and deactivate it if it's currently active
  4. Delete the existing Striking theme
  5. Install the Striking theme version 2.3.5 or later from your theme source (ThemeForest or the vendor directly)
  6. Activate the new version of the Striking theme
  7. Verify the theme is functioning correctly and the path traversal vulnerability is resolved

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

Fix this in Striking 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-2024-37268 — 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-37268 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