LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28047: WordPress Victo theme <= 1.4.16 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28047 affects the WordPress Victo theme by magentech through version 1.4.16. It may allow an unauthenticated remote attacker to include local files through vulnerable PHP include logic. Business risk is high because confidentiality, integrity, and availability are all rated high, but sources do not report active exploitation.

Executive priority

Prioritize review of public WordPress sites using Victo. Treat confirmed installations at or below 1.4.16 as high-risk until vendor guidance or a fixed version is confirmed. Escalation is warranted for internet-facing sites handling sensitive data.

Technical view

The issue is classified as CWE-98: improper control of filename in PHP include/require statements. The CVSS 3.1 score is 8.1, with network access, no privileges, no user interaction, and high attack complexity. The CVE description states the impact is PHP Local File Inclusion in Victo versions through 1.4.16.

Likely exposure

Exposure is likely limited to WordPress sites with the magentech Victo theme installed at version 1.4.16 or earlier. The provided sources do not identify other affected products, forks, plugins, or a confirmed fixed version.

Exploitation context

The CVE is not listed as KEV in the provided bundle. No cited source states active exploitation or provides public exploit status. High attack complexity suggests exploitation may depend on specific site conditions, but the CVSS impact remains severe if exploited.

Researcher notes

Evidence is limited to the CVE record and Patchstack database entry. The source bundle names LFI, CWE-98, and the affected version range, but does not provide root-cause detail, affected parameters, exploit status, or patch availability. Avoid assuming remediation beyond vendor-confirmed guidance.

Mitigation direction

  • Identify WordPress sites using the magentech Victo theme.
  • Check the installed Victo theme version against 1.4.16 or earlier.
  • Review Patchstack and vendor guidance for a fixed release or workaround.
  • If no fix is available, consider disabling or removing the theme where feasible.
  • Restrict administrative access and maintain current WordPress hardening controls.

Validation and detection

  • Inventory WordPress themes across production, staging, and backups.
  • Confirm whether Victo is installed, active, or present but inactive.
  • Record the exact Victo version from WordPress or asset management data.
  • Check security monitoring for unusual requests targeting Victo theme paths.
  • Track the CVE and Patchstack entry for updated remediation details.
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-28047 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-28047Attack 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
magentechVictovicto, 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.