LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32392: WordPress Greenly theme <= 8.1 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Creatives_Planet Greenly greenly allows PHP Local File Inclusion.This issue affects Greenly: from n/a through <= 8.1.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-32392 is a high-severity local file inclusion issue in the WordPress Greenly theme, reported for versions through 8.1. A logged-in attacker may be able to make the site include unintended local files, potentially affecting confidentiality, integrity, and availability. No source provided confirms active exploitation.

Executive priority

Treat as a high-priority triage item if your organization runs WordPress with Greenly. Prioritize public-facing sites and sites with many authenticated users. If Greenly is not used, business urgency is low after verification.

Technical view

The issue is classified as CWE-98: improper control of filenames in PHP include/require statements. CVSS 3.1 is 7.5: AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. The record describes PHP Local File Inclusion in Creatives_Planet Greenly through version 8.1.

Likely exposure

Exposure is likely limited to WordPress sites using the Greenly theme at version 8.1 or earlier. The CVSS vector requires low privileges, so sites with untrusted or numerous authenticated users may face higher practical risk.

Exploitation context

The vulnerability is network-reachable and does not require user interaction, but it requires low privileges and has high attack complexity. The source bundle does not include proof-of-concept details, exploit maturity, or confirmation of exploitation in the wild. It is not listed as KEV in the provided data.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack database reference. The affected-version statement says Greenly through 8.1, while the affected object also contains sparse version data. No patch version, exploit status, or vulnerable parameter is provided in the source bundle.

Mitigation direction

  • Inventory WordPress sites for the Greenly theme and version.
  • If Greenly is installed, check vendor and Patchstack guidance for updates or mitigations.
  • Remove or disable the theme if it is unused, after testing.
  • Reduce unnecessary WordPress accounts and privileges, especially untrusted users.
  • Monitor application and web logs for unusual include-related errors.

Validation and detection

  • Confirm whether Greenly is installed on each WordPress site.
  • Record the installed Greenly version and compare with <= 8.1 exposure.
  • Review the CVE and Patchstack entry for updated remediation guidance.
  • Verify any update, removal, or disabling action in staging first.
  • Check logs for suspicious access patterns or PHP include errors.
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-32392 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-32392Attack 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_PlanetGreenlygreenly, 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.