CVE-2025-68067
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 Core stockholm-core allows PHP Local File Inclusion.This issue affects Stockholm Core: from n/a through <= 2.4.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 confidenceThe Select-Themes Stockholm Core plugin (stockholm-core) versions through 2.4.6 contains a PHP Local File Inclusion (LFI) vulnerability where improper control of filenames in include/require statements allows attackers to include arbitrary local PHP files, potentially leading to code execution.
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.
-
Locate the Stockholm Core plugin installationCheck the wp-content/plugins/ directory for a folder named 'stockholm-core' or search for files containing 'stockholm' and 'core' in the plugins directoryAffected if The Stockholm Core plugin is present in the WordPress plugins directory
-
Identify the installed version of stockholm-coreOpen the plugin's main PHP file or readme.txt and look for the version declaration in the plugin header commentAffected if The version is 2.4.6 or any version prior to the patched release
-
Search for vulnerable file inclusion patternsExamine PHP files in the plugin for include, require, include_once, or require_once statements that use variables or parameters without proper sanitization, particularly looking for dynamic file inclusion where user input could control the file pathAffected if Dynamic file inclusion using unsanitized variables is found in the plugin code
-
Check for accessible parameters that could trigger LFIReview the plugin's PHP files for any GET, POST, or request parameters used in include/require statements without validation, and determine if these endpoints are accessible via web requestsAffected if URL-accessible parameters control file paths in include/require statements
-
Verify PHP allow_url_include settingCreate a temporary PHP script with 'phpinfo();' or check the php.ini configuration for the allow_url_include directiveAffected if allow_url_include is enabled (though this is more relevant for RFI, it indicates a less restrictive PHP configuration)
A user is affected if the Stockholm Core plugin version is 2.4.6 or earlier and the plugin contains dynamic file inclusion code accessible through web request parameters without proper input 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.
From vendor dataUpdate Stockholm Core to the latest patched version if available; otherwise, implement strict input validation on all file inclusion parameters using whitelist validation and disable allow_url_include in PHP configuration.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68067 — 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-68067 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