CVE-2025-31912
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 gavias Enzio - Responsive Business WordPress Theme enzio allows PHP Local File Inclusion.This issue affects Enzio - Responsive Business WordPress Theme: from n/a through < 1.2.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 · high confidenceLocal File Inclusion (LFI) vulnerability in the Gavias Enzio WordPress theme allows attackers to include arbitrary PHP files from the server due to improper control of filenames in include/require statements. This occurs because user-supplied input is used in file inclusion operations without proper validation or sanitization.
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
- 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 Gavias Enzio theme filesNavigate to wp-content/themes/ and check for a folder named 'gavias_enzio', 'enzio', or similar. If the folder exists, the theme is installed.Affected if The theme folder exists in wp-content/themes/
-
Determine installed theme versionOpen the style.css file inside the theme folder and locate the 'Version:' header in the comment block at the top. Record the version number.Affected if Version is missing from style.css or is lower than 1.2.6
-
Verify if theme is activeIn WordPress admin dashboard, go to Appearance > Themes and check if Enzio theme is active (highlighted with 'Active' label).Affected if Theme is currently active and version is below 1.2.6
-
Inspect file inclusion code patternsSearch theme PHP files for 'include', 'require', 'include_once', or 'require_once' statements that use variables without sanitization, particularly patterns like 'include($file)', 'require($_GET[', or similar. Examine files in the theme root and any 'inc/' or 'includes/' subfolders.Affected if Theme contains file inclusion code using unsanitized user input and version is below 1.2.6
User is affected if Gavias Enzio theme is installed and active with a version earlier than 1.2.6, or if the version cannot be determined.
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 · scopedUpdate the Enzio theme to version 1.2.6 or later. If immediate updating is not possible, disable the theme, implement WAF rules to block suspicious file inclusion patterns, and review server access controls.
1.2.6
- Log in to the WordPress admin dashboard
- Navigate to Appearance > Themes
- Locate the gavias Enzio theme
- Check the current version of the theme to confirm it is below 1.2.6
- If an update is available, click 'Update Now' to upgrade to version 1.2.6
- Alternatively, download version 1.2.6 from a trusted source and upload it via Appearance > Themes > Add New > Upload Theme
- Verify the theme was successfully updated to version 1.2.6 or later
- Test the website functionality to ensure the update did not break any features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31912 — 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-31912 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