dbcve.org
Stockholm CoreWordPress extension · Select Themes

CVE-2024-34554

HIGH · 8.8 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 2.4.2 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 Select-Themes Stockholm Core allows PHP Local File Inclusion.This issue affects Stockholm Core: from n/a through 2.4.1.

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 Select-Themes Stockholm Core allows attackers to perform PHP Local File Inclusion by manipulating file path references, potentially enabling remote code execution. The vulnerability exists due to improper validation of path inputs in file inclusion functions.

MitigationUpdate Stockholm Core to the latest version if available, or implement strict input validation and path sanitization on file inclusion parameters to restrict access to allowed directories only.

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
Stockholm CoreWordPress extension
Affected:< 2.4.2

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. Locate Stockholm Core theme installation
    Check your WordPress themes directory (wp-content/themes/stockholm) for the theme files. Look for style.css or theme.json to identify the theme and its version number.
    Affected if Theme is present and version is below 2.4.2
  2. Verify the installed version number
    Open the theme's main style.css file and locate the 'Version:' declaration in the header comment. Compare this version against the affected range: < 2.4.2
    Affected if Version is less than 2.4.2
  3. Identify file inclusion functions in the theme
    Search the theme directory for PHP file inclusion functions (include, include_once, require, require_once) that accept user-controlled path parameters. Look for patterns like 'include($file)', 'require($_GET[...]', or similar dynamic file inclusion.
    Affected if File inclusion functions exist that accept dynamic path input without sanitization
  4. Check for vulnerable path parameter usage
    Examine any file inclusion code for lack of sanitization functions. Look for missing basename(), realpath(), or allowlist validation on path parameters before inclusion.
    Affected if Path parameters are used directly in inclusion functions without validation or sanitization
  5. Test accessibility of file inclusion parameters
    If identified, check if file inclusion parameters (often in query strings like ?file=, ?template=, or ?path=) are accessible to unauthenticated users on the frontend.
    Affected if Unauthenticated users can trigger file inclusion with arbitrary path values

Your environment is affected if Stockholm Core version is below 2.4.2 AND the theme contains file inclusion functionality that accepts unsanitized path parameters accessible to 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.4.2 or later
Fixed in 2.4.2
Interim mitigation

Update Stockholm Core to the latest version if available, or implement strict input validation and path sanitization on file inclusion parameters to restrict access to allowed directories only.

Recommended fix Moderate confidence

Stockholm Core version 2.4.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. If Stockholm Core is the active theme, activate a different temporary theme
  4. Delete the vulnerable Stockholm Core theme (version 2.4.1 or below)
  5. Download Stockholm Core version 2.4.2 or later from a trusted source (Select-Themes marketplace or theme provider)
  6. Upload and install the fixed version via WordPress theme uploader
  7. Activate the updated Stockholm Core theme
  8. Verify the theme is running version 2.4.2 or later by checking the theme details
Caveat Review custom child themes or customizations for compatibility with version 2.4.2 before going live

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

Fix this in Stockholm Core Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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