CVE-2026-32500
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 CreativeWS MetaMax metamax allows PHP Local File Inclusion.This issue affects MetaMax: from n/a through <= 1.1.4.
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 confidenceA Local File Inclusion (LFI) vulnerability exists in CreativeWS MetaMax version 1.1.4 and prior. The application improperly handles filenames in PHP include/require statements, allowing attackers to manipulate file paths and potentially execute arbitrary PHP code from the local server.
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 CreativeWS MetaMax installationSearch the web server document root for files named 'metamax', 'index.php', or directories containing 'MetaMax' in the name. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\Affected if The application files are present on the server
-
Determine installed versionOpen the main PHP file (index.php) or look for a version.php, config.php, or readme.txt file within the application directory. Search for a version string or constant definition (e.g., '$version = "1.1.4"')Affected if The discovered version is 1.1.4 or any version prior to it
-
Identify include/require usage in PHP filesGrep or search all PHP files in the application for 'include', 'require', 'include_once', or 'require_once' statements that reference variables (e.g., include($page), require($_GET['file']))Affected if User-supplied parameters (GET, POST, COOKIE) are used directly in include or require statements without validation
-
Check if vulnerable parameter is accessibleTest the identified parameter by requesting a URL with a manipulated path (e.g., ?page=../../config.php or ?file=/etc/passwd). Observe if the server returns the contents of the targeted fileAffected if The application returns file contents from paths outside the intended directory, confirming LFI is exploitable
The environment is affected if CreativeWS MetaMax version 1.1.4 or prior is installed and PHP files contain include/require statements using unsanitized user input that can be manipulated to access arbitrary local files.
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 sanitization on all parameters used in include/require statements. Use allowlists for permitted files and paths rather than accepting user-supplied filenames directly.
- 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-2026-32500 — 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-2026-32500 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