LiveActive security incident?Get immediate response
CVE Record

CVE-2025-26757: WordPress FULL – Cliente plugin <= 3.1.26 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in FULL SERVICES FULL Customer full-customer allows PHP Local File Inclusion.This issue affects FULL Customer: from n/a through <= 3.1.26.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-26757 affects the WordPress FULL Customer plugin, also described as FULL - Cliente, through version 3.1.26. The flaw may let an attacker include local PHP files, potentially affecting confidentiality, integrity, and availability. The supplied sources do not confirm active exploitation or a fixed version.

Executive priority

Prioritize this for any internet-facing WordPress property using the plugin. The impact rating is high, but urgency depends on confirmed deployment, plugin version, and whether vendor remediation exists. Absence from KEV lowers evidence of active exploitation, not potential business impact.

Technical view

The issue is classified as CWE-98: improper filename control in PHP include/require logic. The CVSS 3.1 score is 7.5 with network attack vector, high attack complexity, no privileges required, and user interaction required. Scope is unchanged, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites running FULL SERVICES FULL Customer, package full-customer, at versions through 3.1.26. The bundle provides no CPEs and has limited affected-version detail, so asset validation should rely on plugin inventory rather than CPE matching.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. The CVSS vector indicates exploitation is remote but has high complexity and requires user interaction. No source in the bundle confirms public exploitation, exploit code, or observed attacks.

Researcher notes

The source bundle has a wording mismatch: it names PHP Remote File Inclusion while describing PHP Local File Inclusion. Affected-version data is sparse and includes no CPEs. Do not assume exploitability beyond the CVSS vector and CVE description without vendor or researcher confirmation.

Mitigation direction

  • Inventory WordPress sites for the FULL Customer or FULL - Cliente plugin.
  • If installed at version 3.1.26 or earlier, treat it as high priority.
  • Check vendor and Patchstack guidance for a fixed version or official mitigation.
  • If no fix exists, consider disabling the plugin after business impact review.
  • Restrict administrative access and monitor affected sites until remediation is confirmed.

Validation and detection

  • Confirm plugin name, package identifier full-customer, and installed version from WordPress inventory.
  • Compare detected versions against the affected range through 3.1.26.
  • Review CVE and Patchstack entries for updated fix or mitigation status.
  • Check logs for unusual file include errors or unexpected PHP path references.
  • Document whether each WordPress site is affected, remediated, or not applicable.
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-2025-26757 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:N/UI:R/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:N/UI:R/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-2025-26757Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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
FULL SERVICESFULL Customerfull-customer, 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.