LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22416: WordPress FixTeam theme <= 1.5.0 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22416 affects the AncoraThemes FixTeam WordPress theme through version 1.5.0. It is a local file inclusion issue that may let an unauthenticated remote attacker access or impact server-side files. The CVSS score is high at 8.1, but exploitation is rated high complexity and no active exploitation evidence is provided.

Executive priority

Treat as a high-priority WordPress exposure if your organization uses the FixTeam theme on public sites. Immediate action is inventory and vendor-guidance tracking, because the available sources do not name a fixed release. Remove unused installations to reduce risk.

Technical view

The issue is CWE-98: improper control of a filename used in a PHP include/require statement. The CVE description calls it PHP Local File Inclusion in FixTeam through <=1.5.0. CVSS 3.1 is 8.1: network-accessible, unauthenticated, no user interaction, high complexity, with high confidentiality, integrity, and availability impact.

Likely exposure

Public WordPress sites using AncoraThemes FixTeam theme version 1.5.0 or earlier are the relevant exposure. The source data does not identify a fixed version or whether inactive installations are affected, so teams should inventory installed theme versions directly.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. The vulnerability is remotely reachable and unauthenticated per CVSS, but attack complexity is high. The practical risk depends on site configuration and the vulnerable theme code path.

Researcher notes

There is a version-detail inconsistency: the CVE bundle states through <=1.5.0, while the Patchstack reference URL text mentions 1.4. The structured CVE description should be treated as authoritative unless Patchstack or the vendor clarifies. No exploit details or patch version are present in the provided sources.

Mitigation direction

  • Identify all WordPress sites with the FixTeam theme installed.
  • Check AncoraThemes, Patchstack, and CVE updates for a fixed version or vendor guidance.
  • Remove the FixTeam theme if it is not required.
  • Apply vendor-provided updates when available after testing.
  • Consider provider WAF or virtual patching if supported.

Validation and detection

  • Confirm FixTeam theme presence and exact version on each WordPress site.
  • Prioritize versions 1.5.0 and earlier for remediation review.
  • Review web logs for unusual requests targeting theme PHP files.
  • Monitor Patchstack and CVE records for updated remediation details.
  • Document whether affected sites are internet-facing.
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-22416 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-22416Attack 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
AncoraThemesFixTeamfixteam, 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.