CVE-2026-32504
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 VintWood vintwood allows PHP Local File Inclusion.This issue affects VintWood: from n/a through <= 1.1.8.
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 confidenceThe VintWood theme <= 1.1.8 contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in include/require statements. This allows attackers to include arbitrary local PHP files, potentially leading to remote code execution or disclosure of sensitive server files.
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 VintWood theme and identify versionCheck the theme directory (commonly wp-content/themes/vintwood for WordPress) and read the version from style.css header or version.php file. Compare the version number to 1.1.8.Affected if The theme is installed and version is 1.1.8 or lower
-
Identify PHP files with dynamic include/require statementsSearch the theme directory for PHP files containing include(), require(), include_once(), or require_once() with variables in the path (e.g., include($var), include($_GET['page']).Affected if Dynamic file inclusion using variables is present in any theme PHP file
-
Trace user input to file inclusion functionsExamine the identified include/require statements to determine if GET, POST, or COOKIE parameters flow directly into the file path without sanitization or validation.Affected if User-supplied input (REQUEST, GET, POST parameters) reaches the include/require without validation
-
Check for path traversal vulnerabilityTest whether the file inclusion parameter accepts path traversal sequences like ../ to access files outside the theme directory.Affected if The parameter allows .. / path traversal to traverse directories
You are affected if VintWood theme version 1.1.8 or lower is installed AND dynamic file inclusion with unsanitized user input is present in the theme.
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 on all file inclusion parameters, using whitelist validation for allowed files/directories and rejecting any input containing path traversal sequences (..). Prefer hardcoded includes over dynamic ones.
- 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-2026-32504 — 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-32504 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