DwellWordPress extension · Axiomthemes
CVE-2025-58942
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 axiomthemes Dwell dwell allows PHP Local File Inclusion.This issue affects Dwell: from n/a through <= 1.7.0.
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 Dwell WordPress theme by axiomthemes contains a PHP Local File Inclusion (LFI) vulnerability where user-controlled input is used in include/require statements without proper validation. This allows attackers to include arbitrary local PHP files, potentially leading to remote code execution.
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
DwellWordPress extension
<= 1.7.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Confirm Dwell theme is installedNavigate to WordPress admin > Appearance > Themes and verify the Dwell theme by axiomthemes is active or installedAffected if The Dwell theme is present in the WordPress installation
-
Identify the installed Dwell theme versionIn WordPress admin, go to Appearance > Themes, click on the Dwell theme details, and note the version number displayedAffected if The installed version is 1.7.0 or lower
-
Locate theme files with include or require statementsAccess the WordPress file system via FTP or file manager, navigate to wp-content/themes/dwell/, and search PHP files for include, require, include_once, or require_once statements that use variables in the pathAffected if PHP files contain include/require statements using user-supplied input without sanitization
-
Identify the vulnerable parameterExamine the include/require statements found for dynamic variable usage (e.g., include($_GET['file'])), noting which request parameter controls the file pathAffected if A parameter (such as 'file', 'path', 'template', or similar) is used directly in file inclusion logic without validation
-
Test if the file inclusion is exploitableSend a crafted request to the affected endpoint using the vulnerable parameter (e.g., ?file=../../../../wp-config.php) and observe if the file contents are returnedAffected if The parameter accepts path traversal sequences and returns file contents, confirming the LFI is present and accessible
The environment is affected if the Dwell theme version is 1.7.0 or lower AND the theme contains dynamic file inclusion code using unsanitized user input that can be triggered via HTTP request parameters.
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 to a patched version of the Dwell theme. If no patch is available, implement strict input validation on any parameters used in file inclusion paths and disable allow_url_include in PHP configuration.
Fix this in Dwell
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58942 — 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-58942 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