StockholmWordPress extension · Select Themes
CVE-2024-34551
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 WordPress theme (versions through 9.6) allows unauthenticated attackers to traverse directories and include arbitrary PHP files, potentially leading to remote code execution. The CVSS 9.8 score indicates this is remotely exploitable without authentication and can result in complete system compromise.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if Stockholm theme is installedNavigate to Appearance > Themes in WordPress admin dashboard and look for Stockholm theme in the installed themes list. Note whether it is the active theme.Affected if Stockholm theme is installed and/or active on the WordPress site
-
Determine installed Stockholm theme versionAccess the theme's style.css file via file manager or FTP at wp-content/themes/stockholm/style.css and locate the 'Version:' comment in the file header, or check the theme version displayed in the WordPress admin theme details panel.Affected if Version displayed is less than 9.7 (e.g., 9.6, 9.5, etc.)
-
Check for suspicious access to theme filesReview web server access logs (Apache access.log, Nginx access.log) for requests to theme files with directory traversal patterns such as '../', '..\', or requests to non-standard theme paths. Example suspicious pattern: GET /?theme=stockholm&file=../../wp-config.phpAffected if Unusual traversal patterns found in logs accessing Stockholm theme files
-
Inspect theme directory for unauthorized modificationsCompare current theme files in wp-content/themes/stockholm/ against a known clean backup or the official theme distribution. Look for newly created PHP files with random names, modified existing PHP files, or base64-encoded strings in files.Affected if New or modified PHP files found in the theme directory that were not part of the original theme distribution
You are affected if the Stockholm theme version is below 9.7 and the theme is installed on your WordPress site, as this version range contains the path traversal vulnerability allowing unauthenticated remote code execution.
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
Update Stockholm theme to version 9.7 or later to patch the path traversal vulnerability. If no patch is available, disable the theme and deploy an alternative theme while monitoring for exploitation attempts.
Stockholm theme version 9.7
- Backup your website before making any changes
- Update the Stockholm theme to version 9.7 or later through your WordPress dashboard (Appearance > Themes) or via FTP upload of the new version
- Verify the update was successful by checking the theme version in Appearance > Themes
- Clear any caching mechanisms after the update
- Test critical functionality to ensure the theme works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Stockholm
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34551 — 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-34551 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