LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32393: WordPress Greenly Theme Addons plugin < 8.2 - Local File Inclusion vulnerability

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-32393 affects the WordPress Greenly Theme Addons plugin before version 8.2. A logged-in attacker may be able to force the site to include unintended local files, potentially exposing sensitive data or affecting site integrity and availability. No provided source states active exploitation.

Executive priority

Treat as high priority for sites running this plugin, especially public WordPress sites with multiple user accounts. It is not currently listed as known exploited in the provided data, but the potential site impact is high if an attacker has valid low-level access.

Technical view

The CVE describes improper filename control in a PHP include/require path, mapped to CWE-98 and characterized as PHP Local File Inclusion. CVSS 3.1 is 7.5: network-accessible, high complexity, low privileges required, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites using Creatives_Planet Greenly Theme Addons, package greenly-addons, versions below 8.2. Sites without this plugin, or on 8.2 or later per the CVE description, are not indicated as affected.

Exploitation context

The CVSS vector indicates exploitation requires network access and low privileges, but no user interaction. Attack complexity is high. The source bundle does not include exploit details, proof-of-concept availability, or evidence of active exploitation; KEV status is false.

Researcher notes

Public details are limited. The CVE and Patchstack entry identify the affected plugin and version boundary but do not provide safe technical indicators, exploit status, or detailed remediation beyond the version threshold. Avoid assuming unauthenticated exploitation or active exploitation from the available evidence.

Mitigation direction

  • Inventory WordPress sites for the Greenly Theme Addons plugin.
  • Update Greenly Theme Addons to version 8.2 or later if available.
  • If update is unavailable, consult vendor or Patchstack guidance before using compensating controls.
  • Remove or disable the plugin where it is not business-critical.
  • Restrict unnecessary WordPress user accounts and review low-privilege access.

Validation and detection

  • Confirm whether greenly-addons is installed on each WordPress instance.
  • Record the installed plugin version and compare it with 8.2.
  • Verify the plugin is updated, removed, or otherwise addressed.
  • Review WordPress accounts for unnecessary low-privilege access.
  • Monitor vendor, CVE, and Patchstack pages for updated remediation details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32393 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-32393Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Creatives_PlanetGreenly Theme Addonsgreenly-addons, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.