CVE-2025-68068
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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Select-Themes Stockholm stockholm allows PHP Local File Inclusion.This issue affects Stockholm: from n/a through <= 9.14.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 confidenceA Local File Inclusion (LFI) vulnerability in the Stockholm WordPress theme allows attackers to manipulate file inclusion parameters to include arbitrary local PHP files. This occurs due to improper control of filenames in include/require statements, potentially enabling code execution or sensitive file disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 your WordPress installation at wp-content/themes/stockholm/Affected if The Stockholm theme directory exists in your WordPress themes folder
-
Identify the Stockholm theme versionOpen the theme's style.css file (wp-content/themes/stockholm/style.css) and look for the 'Version:' header in the comment block at the top, or check theme.json for a version fieldAffected if You cannot determine the version or the version is not the latest patched release
-
Locate vulnerable file inclusion codeSearch PHP files in the theme directory for include/require statements using variables in the path (e.g., include($_GET['file']), require($path), include_once($_REQUEST['template'])) without proper sanitization. Common patterns include: include($_GET['include']), require($_POST['file']), include($theme_dir.'/'.$_GET['template'])Affected if PHP files in the theme contain include/require statements that directly use user-controlled input without sanitization
-
Verify the vulnerable parameters are accessibleCheck if the identified file inclusion variables are passed via GET or POST parameters that can be controlled by unauthenticated users. Test by examining the code flow from input to the include statement, checking if any authentication or validation occurs between the parameter input and the include/require callAffected if Unauthenticated users can influence the file path parameter that reaches the vulnerable include/require statement
Your environment is affected if the Stockholm theme is installed and the version has not been patched, the theme contains file inclusion code using unsanitized user input, and the affected parameters are accessible to unauthenticated users.
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 dataUpdate the Stockholm theme to the latest patched version immediately. If patching is delayed, implement input validation on file path parameters and consider deploying a WAF rule to block suspicious file inclusion requests.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68068 — 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-2025-68068 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