CVE-2025-32294
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 Oxpitan oxpitan allows PHP Local File Inclusion.This issue affects Oxpitan: from n/a through <= 1.3.5.
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 PHP Local File Inclusion (LFI) vulnerability in the gavias Oxpitan theme where improper control of filenames in include/require statements allows attackers to read sensitive files from the local server by manipulating path parameters.
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.
-
Identify if Gavias Oxpitan theme is installedSearch your web application file structure for directories or files named 'gavias', 'oxpitan', or theme configuration files associated with the Gavias Oxpitan theme.Affected if The Gavias Oxpitan theme files are present in your webroot or application directory.
-
Locate PHP files with include/require statementsSearch within the theme directory for PHP files using grep or similar tools to find lines containing 'include', 'require', 'include_once', or 'require_once' that reference variables in the path.Affected if The theme contains PHP files that use dynamic file inclusion with variables in the path argument.
-
Identify user-controlled path parametersReview the identified include/require statements to determine if any path variables are populated from HTTP request parameters (e.g., $_GET, $_POST, $_REQUEST).Affected if File inclusion paths are constructed using values from user-supplied input without sanitization.
-
Check for parameter exposure in routes or controllersExamine your application's routing configuration, URL parameters, and any files that handle request parameters to see if path-related parameters are passed to include/require functions.Affected if URL parameters or other user input can influence which files are included or required by the PHP code.
-
Verify file access restrictionsInspect the include/require logic to confirm whether any whitelist validation, base path restriction, or input sanitization is performed before the file inclusion occurs.Affected if The code directly uses user input in file inclusion statements without validation or with insufficient restrictions.
Your environment is affected if the Gavias Oxpitan theme is installed and its PHP code uses include/require statements with user-controlled path parameters that lack proper 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 whitelisting for file inclusion parameters, ensuring only allowed files/directories can be accessed; avoid using user input directly in include/require statements.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32294 — 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-32294 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