LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32503: WordPress Trendustry theme <= 1.1.4 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-32503 affects the WordPress Trendustry theme through version 1.1.4. A remote, unauthenticated attacker may be able to force the site to include unintended local files, potentially exposing data or affecting site integrity and availability. The public record rates it high severity. No cited source confirms active exploitation.

Executive priority

Treat this as a high-priority WordPress exposure check, especially for public sites using Trendustry. Urgency is driven by unauthenticated network reachability and potential high impact, not by confirmed active exploitation. Focus first on identifying affected sites and obtaining vendor remediation guidance.

Technical view

The CVE describes improper filename control in a PHP include/require statement in CreativeWS Trendustry, resulting in local file inclusion. CVSS 3.1 is 8.1 with AV:N/AC:H/PR:N/UI:N and high confidentiality, integrity, and availability impact. The affected range is Trendustry through 1.1.4.

Likely exposure

Exposure is limited to WordPress sites using the CreativeWS Trendustry theme at version 1.1.4 or earlier. Internet-facing WordPress deployments are the primary concern because the CVSS vector indicates network access and no required authentication.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source confirms exploitation in the wild. Exploitation is rated high complexity, but successful abuse could have serious impact. Public information does not include safe technical details or a confirmed fixed version.

Researcher notes

The public data is sparse. The CVE lists CWE-98 and references PHP include/require filename control, while the description names local file inclusion. The affected range is through 1.1.4, but the provided sources do not name a patched version or detailed root-cause location.

Mitigation direction

  • Inventory WordPress sites for the Trendustry theme and record installed versions.
  • If Trendustry is version 1.1.4 or earlier, prioritize remediation planning.
  • Check CreativeWS, WordPress theme channels, and Patchstack for fixed-version guidance.
  • Update to a vendor-confirmed fixed release if one is available.
  • If no fix exists, consider disabling or replacing the theme where feasible.

Validation and detection

  • Confirm whether Trendustry is installed on each WordPress site.
  • Verify the installed Trendustry version is greater than 1.1.4 or vendor-marked fixed.
  • Review web and WordPress logs for unusual file-related request patterns.
  • Document sites where no vendor fix is available and track compensating actions.
  • Monitor CVE and Patchstack entries for revised affected-version or fix information.
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-32503 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
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/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
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:N/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
CreativeWSTrendustrytrendustry, n/aunaffected
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.