CVE-2025-67523
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 trippleS Exhibz exhibz allows PHP Local File Inclusion.This issue affects Exhibz: from n/a through <= 3.0.9.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the Exhibz WordPress theme. The vulnerability allows attackers to manipulate filename parameters in PHP include/require statements to read sensitive local files from the server, potentially exposing system configuration files, credentials, or other sensitive data.
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 Exhibz theme is installedNavigate to wp-content/themes/ in your WordPress installation and check for a folder named 'exhibz' or similar variant. List all theme directories to identify if Exhibz is present.Affected if The exhibz theme directory exists in the WordPress themes folder.
-
Determine Exhibz theme versionOpen the style.css file within the Exhibz theme folder and locate the 'Version:' header in the file comments at the top. Alternatively, check theme.json for a version field.Affected if The installed version is lower than the latest patched version, or the version cannot be determined (indicating an older release).
-
Identify file inclusion code patternsSearch the Exhibz theme directory for PHP files containing include, require, include_once, or require_once statements that use variables in the file path (e.g., include($file), require($_GET['filename']). Use grep or manually review PHP files in the theme folder.Affected if The theme contains include/require statements that incorporate user-supplied input directly into the file path without sanitization.
-
Check for exposed file parameter handlersReview PHP files that handle request parameters (GET/POST) related to file loading, template inclusion, or page rendering. Look for parameters that might control which files are included, such as 'file', 'template', 'page', or 'filename'.Affected if URL parameters can be manipulated to specify arbitrary file paths for inclusion, allowing LFI exploitation.
You are affected if the Exhibz theme is installed and contains vulnerable file inclusion code that accepts user-supplied input without validation, regardless of the specific version.
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 the latest version of Exhibz when available. Until then, implement strict input validation with allowlist filtering on file inclusion parameters and avoid using user-supplied input directly in include/require statements.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67523 — 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-67523 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