FabricWordPress extension · Axiomthemes
CVE-2025-58941
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 Fabric fabric allows PHP Local File Inclusion.This issue affects Fabric: from n/a through <= 1.5.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 confidenceLocal File Inclusion vulnerability in axiomthemes Fabric theme allows attackers to control filenames used in PHP include/require statements, potentially enabling execution of arbitrary PHP code by including malicious local files.
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
FabricWordPress extension
<= 1.5.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.
-
Locate the Fabric theme installationSearch your web server directories for the 'fabric' theme folder, typically found in wp-content/themes/fabric for WordPress installations or similar theme directories for other platforms.Affected if The Fabric theme folder exists on the server and contains PHP files.
-
Identify the installed versionOpen the theme's style.css file or main PHP configuration file and look for a 'Version:' header or $version variable declaration.Affected if The version is 1.5.0 or lower.
-
Find PHP files with include/require statementsSearch the theme directory for PHP files containing 'include(', 'require(', 'include_once(', or 'require_once(' statements, particularly in files that handle user requests.Affected if PHP files contain dynamic file inclusion using variables or parameters without sanitization.
-
Inspect file inclusion parameters for user inputExamine the identified include/require statements and trace whether $_GET, $_POST, or $_REQUEST parameters are used directly in the file path without validation or whitelisting.Affected if User-supplied input from request parameters is used directly in include/require statements without filtering.
-
Check for vulnerable file handlersReview PHP files that process query parameters (such as 'page', 'file', 'template', or 'path') and pass them to include/require functions.Affected if URL parameters control which files are included and no whitelist or sanitization is applied.
Your environment is affected if the Fabric theme version is 1.5.0 or lower AND PHP files in the theme use user-controlled input in include/require statements without 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 dataImplement strict input validation and whitelist-based filtering on all file inclusion parameters; avoid user-supplied input in include/require statements entirely or use a whitelist of allowed files.
Fix this in Fabric
Scoped from the published advisory
- 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-58941 — 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-58941 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