LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27996: WordPress Lingvico theme <= 1.0.14 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27996 affects the WordPress Lingvico theme by ThemeREX through version 1.0.14. It may let an unauthenticated remote attacker include local files through unsafe PHP include handling. The reported impact is high for confidentiality, integrity, and availability. There is no KEV listing in the provided sources, so active exploitation is not confirmed here.

Executive priority

Treat this as a high-priority WordPress exposure review. The risk is serious for affected public sites, but urgency should be based on whether Lingvico is installed and whether vendor remediation is available. No confirmed active exploitation is cited in the provided sources.

Technical view

The issue is classified as CWE-98: improper control of filename for PHP include/require. The CVSS 3.1 score is 8.1 with network attack vector, no privileges, no user interaction, high complexity, and high CIA impact. The public record identifies Lingvico versions through 1.0.14 as affected.

Likely exposure

Exposure is limited to WordPress sites with the ThemeREX Lingvico theme installed at version 1.0.14 or earlier. The source bundle does not identify affected plugins, other ThemeREX products, or specific hosting configurations.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation is possible but high complexity. The provided sources do not confirm public exploit availability or active exploitation. This is not listed as CISA KEV in the supplied data.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack vulnerability entry. The affected range is stated as Lingvico through 1.0.14. The bundle does not provide vulnerable parameters, proof-of-concept details, exploit telemetry, or a named fixed release.

Mitigation direction

  • Inventory WordPress sites for the Lingvico theme and record installed versions.
  • Prioritize sites running Lingvico version 1.0.14 or earlier.
  • Check ThemeREX, Patchstack, and CVE guidance for an official fixed version or mitigation.
  • If no fix is available, consider disabling or replacing the theme where operationally feasible.
  • Back up sites before theme changes and test changes in staging when possible.

Validation and detection

  • Confirm whether the active or installed theme package is Lingvico.
  • Verify the installed Lingvico version is greater than 1.0.14, if a fixed version exists.
  • Review web logs for unusual file-include style requests without reproducing exploit behavior.
  • Confirm compensating controls, such as WAF rules, are enabled where available.
  • Track the CVE and Patchstack entry for updates to affected versions or remediation.
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-27996 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-27996Attack 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
ThemeREXLingvicolingvico, 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.