dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-32537

HIGH · 7.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in nK Visual Portfolio, Photo Gallery & Post Grid visual-portfolio allows PHP Local File Inclusion.This issue affects Visual Portfolio, Photo Gallery & Post Grid: from n/a through <= 3.5.1.

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 confidence

The nK Visual Portfolio plugin for WordPress versions through 3.5.1 contains a Local File Inclusion (LFI) vulnerability where improper control of filename parameters in include/require statements allows attackers to include arbitrary local PHP files. This can lead to sensitive file disclosure or potentially remote code execution if an attacker can upload files to accessible locations.

MitigationUpdate the Visual Portfolio, Photo Gallery & Post Grid plugin to the latest version. If immediate patching is not possible, disable the plugin and review server access logs for suspicious file access attempts. Audit other WordPress plugins for similar file inclusion vulnerabilities.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Visual Portfolio plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder containing 'visual-portfolio' or 'nk-visual-portfolio'. Check the plugin's main PHP file header for the Version field.
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    Open the main plugin file (typically visual-portfolio.php or index.php in the plugin folder) and locate the 'Version:' header comment, or check the plugin row in WordPress admin plugins list.
    Affected if Version is 3.5.1 or lower (the vulnerability affects versions through 3.5.1)
  3. Identify vulnerable include/require code
    Search plugin PHP files for dynamic include/require statements using variables or request parameters without sanitization (e.g., include($_GET['file']), require($var)). Focus on files in include/ or classes/ directories.
    Affected if Code contains unsanitized file inclusion using user-controlled input (GET/POST parameters)
  4. Review server access logs for LFI patterns
    Examine Apache/nginx access logs for requests to the plugin containing path traversal sequences (e.g., ../../) or direct PHP file references in query parameters. Look for unusual files being requested.
    Affected if Logs show requests with ../ sequences or attempts to include files outside the plugin directory
  5. Verify upload directory accessibility
    Check wp-content/uploads/ and plugin upload folders for world-writable permissions or unexpected uploaded PHP files that could be included via the LFI flaw.
    Affected if Uploads directory is web-accessible and contains executable PHP files placed by an attacker

You are affected if the Visual Portfolio plugin version is 3.5.1 or lower AND your server contains the vulnerable dynamic file inclusion code pattern accessible via web request.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Visual Portfolio, Photo Gallery & Post Grid plugin to the latest version. If immediate patching is not possible, disable the plugin and review server access logs for suspicious file access attempts. Audit other WordPress plugins for similar file inclusion vulnerabilities.

Recommended fix Moderate confidence

Latest version of Visual Portfolio, Photo Gallery & Post Grid (contact vendor or check WordPress plugin repository for the specific fixed release)

  1. 1. Update Visual Portfolio, Photo Gallery & Post Grid plugin to the latest available version
  2. 2. Verify the update was applied successfully by checking the plugin version in WordPress admin
  3. 3. Confirm the vulnerability is resolved by testing that arbitrary file inclusion is no longer possible
  4. 4. If automatic updates are enabled, verify the site received the security update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32537 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32537 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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