LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32500: WordPress MetaMax 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 MetaMax metamax allows PHP Local File Inclusion.This issue affects MetaMax: 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-32500 affects the WordPress MetaMax theme through version 1.1.4. It can allow an unauthenticated remote attacker to make PHP include local files. The CVSS score is 8.1, reflecting potentially high confidentiality, integrity, and availability impact. No public source provided confirms active exploitation.

Executive priority

Treat as high priority for any public WordPress site using MetaMax. The issue is unauthenticated and has high impact ratings, but exploitation complexity is high and no active exploitation is confirmed in the provided sources.

Technical view

The CVE describes improper control of a filename used in a PHP include/require statement, mapped to CWE-98. Affected product is CreativeWS MetaMax, package metamax, through version 1.1.4. The vector is network-accessible, unauthenticated, no user interaction, high complexity, with high CIA impact.

Likely exposure

Exposure is likely limited to WordPress sites that have the CreativeWS MetaMax theme installed at version 1.1.4 or earlier. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates exploitation is remote and unauthenticated but high complexity. The source bundle does not include exploit details, proof-of-concept status, or confirmation of exploitation in the wild. The CVE is not listed as KEV in the provided data.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The affected range is stated as through 1.1.4, with default status listed as unaffected outside that range. No patch version, exploit maturity, vulnerable parameter, or detailed technical advisory is present in the source bundle.

Mitigation direction

  • Inventory WordPress sites for the MetaMax theme and its installed version.
  • If MetaMax is unused, remove or disable it.
  • For affected installs, check CreativeWS or Patchstack guidance for a fixed version or workaround.
  • Prioritize replacement or compensating controls if no vendor fix is available.
  • Monitor WordPress and web application logs for suspicious theme-related requests.

Validation and detection

  • Confirm whether the MetaMax theme is installed on each WordPress site.
  • Record the installed MetaMax version and flag versions 1.1.4 or earlier.
  • Review vendor and Patchstack advisories for updated remediation information.
  • Check whether any security plugin or WAF has a relevant virtual patch.
  • Review logs for unusual file-include style request patterns without testing exploit payloads.
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-32500 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-32500Attack 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
CreativeWSMetaMaxmetamax, 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.