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

CVE-2026-32393

HIGH · 7.5 CVSS v3.1 Published 2026-03-13
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 Creatives_Planet Greenly Theme Addons greenly-addons allows PHP Local File Inclusion.This issue affects Greenly Theme Addons: from n/a through < 8.2.

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 · high confidence

A Local File Inclusion (LFI) vulnerability exists in the Creatives_Planet Greenly Theme Addons plugin (greenly-addons) for WordPress. The vulnerability allows unauthenticated attackers to include arbitrary PHP files from the server through improper validation of file path parameters in include/require statements, potentially leading to sensitive file disclosure or remote code execution. The vulnerability affects versions prior to 8.2.

MitigationUpgrade Greenly Theme Addons to version 8.2 or later. If upgrading is not immediately possible, disable the plugin and implement web application firewall rules to block directory traversal patterns in request 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
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 Greenly Theme Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Greenly Theme Addons' or 'Creatives Planet' plugin. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'greenly' in the name.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, click on the plugin from the Plugins list to view its details, or open the main plugin PHP file and locate the 'Version' header in the plugin comments. Compare the version number to 8.2.
    Affected if The installed version is any version prior to 8.2 (e.g., 8.1, 8.0, 7.x, etc.)
  3. Locate dynamic file inclusion calls
    Examine PHP files within the plugin directory for patterns such as include(), require(), include_once(), or require_once() that accept variables as file paths. Search the plugin files for these functions combined with $_GET, $_POST, or $_REQUEST superglobals.
    Affected if The plugin contains dynamic file inclusion that uses unsanitized user input
  4. Verify lack of input validation on file path parameters
    Review the identified inclusion code to determine whether the file path parameter undergoes validation (such as allowlisting, basename(), realpath(), or regex checks) before being used. Look for direct usage like include($_GET['file']) without sanitization.
    Affected if File path parameters are used directly without validation or sanitization
  5. Check for directory traversal protection
    Examine whether the plugin code prevents path traversal sequences like ../ or ..\ from being passed in file path parameters. Look for absence of code that blocks or normalizes these sequences.
    Affected if No protection against directory traversal patterns exists in the file inclusion logic

A user is affected if the Greenly Theme Addons plugin is installed with any version lower than 8.2 and the plugin contains dynamic file inclusion using unsanitized user-supplied parameters.

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

Upgrade Greenly Theme Addons to version 8.2 or later. If upgrading is not immediately possible, disable the plugin and implement web application firewall rules to block directory traversal patterns in request parameters.

Recommended fix Moderate confidence

Version 8.2 or later

  1. Upgrade the Greenly Theme Addons (greenly-addons) to version 8.2 or later to remediate the PHP Local File Inclusion vulnerability

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32393 — 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-32393 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