StockholmWordPress extension · Select Themes
CVE-2024-34552
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 Select-Themes Stockholm allows PHP Local File Inclusion.This issue affects Stockholm: from n/a through 9.6.
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 the Stockholm theme allows attackers to manipulate file paths and include arbitrary PHP files from the local server, potentially leading to code execution or sensitive data exposure. The vulnerability stems from insufficient input validation on file path parameters.
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
StockholmWordPress extension
< 9.7CVSS 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 Stockholm theme is installedLocate the Stockholm theme directory in the WordPress installation under wp-content/themes/ and verify the theme files are presentAffected if The Stockholm theme files exist in the themes directory
-
Check the installed version numberOpen the theme's style.css file (or version.php if present) and locate the Version: header to read the version stringAffected if The reported version is lower than 9.7 (e.g., 9.6, 9.5, etc.)
-
Identify file inclusion code patternsSearch the theme's PHP files for dynamic include, require, or similar functions that accept variables in their path parametersAffected if File inclusion functions use unvalidated user-supplied input for file paths
-
Review web server access logs for path traversal attemptsExamine HTTP access logs for requests containing traversal sequences (such as ../) or unusual file path parameters directed at Stockholm theme endpointsAffected if Logs show suspicious requests with path traversal patterns targeting the theme
-
Audit file upload and inclusion featuresIdentify any theme features that accept file paths or allow file inclusion, then verify whether input validation is applied to path parametersAffected if File inclusion features exist and accept user-controlled paths without validation
The environment is affected if the Stockholm theme is installed with a version number lower than 9.7 and contains file inclusion functionality that processes user-supplied path parameters without proper validation.
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.
dbcve · scoped9.7
Implement strict input validation and sanitization for all file path parameters, use whitelist approaches for allowed files/directories, and validate that resolved paths stay within intended directories.
Stockholm version 9.7 or later
- Upgrade the Stockholm theme to version 9.7 or later to resolve the path traversal vulnerability
- After upgrading, verify that the Local File Inclusion vulnerability is no longer exploitable
- Ensure that any custom code or child themes do not reintroduce similar path traversal vulnerabilities
- Consider reviewing server-side file access controls as a defense-in-depth measure
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Stockholm
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34552 — 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-34552 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