LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22504: WordPress ProLingua theme <= 1.1.12 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22504 affects the ThemeREX ProLingua WordPress theme through version 1.1.12. It can let an unauthenticated attacker include local server files through vulnerable PHP handling. The published severity is high, but exploitation difficulty is marked high. No provided source confirms active exploitation.

Executive priority

Treat as a high-priority web exposure review for WordPress properties using ProLingua. Prioritize internet-facing and revenue-critical sites. Urgency is elevated by potential confidentiality, integrity, and availability impact, but current sources do not confirm exploitation in the wild.

Technical view

The issue is CWE-98: improper control of filenames in PHP include/require statements, described as PHP local file inclusion. CVSS 3.1 is 8.1 with AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Affected scope is ProLingua versions up to and including 1.1.12, based on the CVE description.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX ProLingua theme through version 1.1.12. Organizations without this theme are not exposed based on the provided sources. The source bundle does not identify hosting environments, configuration prerequisites, or a fixed version.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation with no user interaction, but high attack complexity. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation or public exploit availability.

Researcher notes

Available public detail is sparse. The CVE and Patchstack entry identify LFI in ProLingua <= 1.1.12, but the provided sources do not name a vulnerable parameter, proof of concept, patch version, or exploitation telemetry. Avoid assuming broader ThemeREX product impact.

Mitigation direction

  • Inventory WordPress sites for the ProLingua theme and its installed version.
  • If version is 1.1.12 or older, check ThemeREX and Patchstack guidance immediately.
  • If no safe update is confirmed, consider disabling or replacing the theme temporarily.
  • Restrict administrative access and ensure backups are current before remediation changes.

Validation and detection

  • Confirm whether each WordPress site has the ProLingua theme installed.
  • Record the installed ProLingua version and compare it to <= 1.1.12.
  • Review web logs for unusual requests targeting theme PHP files or file path parameters.
  • Document whether vendor guidance, an update, or compensating controls were applied.
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-22504 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-22504Attack 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
ThemeREXProLinguaprolingua, 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.