LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22415: WordPress The Mounty theme <= 1.1 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes The Mounty the-mounty allows PHP Local File Inclusion.This issue affects The Mounty: from n/a through <= 1.1.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22415 affects the WordPress theme The Mounty through version 1.1. It may let an unauthenticated remote attacker include local files through unsafe PHP include/require handling. Business urgency is high for sites using this theme, but the source bundle does not show active exploitation or a named fixed version.

Executive priority

Treat as a priority if The Mounty is present on public WordPress sites. The potential impact is high, but urgency depends on confirmed use of the theme. No active exploitation is evidenced in the provided sources.

Technical view

The issue is classified as CWE-98: improper control of filenames in PHP include/require statements. The CVSS 3.1 score is 8.1, with network access, no privileges, no user interaction, high attack complexity, and high confidentiality, integrity, and availability impact. The record describes PHP Local File Inclusion in AncoraThemes The Mounty.

Likely exposure

Exposure is likely limited to WordPress sites running AncoraThemes The Mounty version 1.1 or earlier. The site must be reachable by attackers. The CVSS vector indicates authentication is not required, but exploitation is high complexity.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV in the source bundle. Public disclosure exists through CVE and Patchstack database references. No exploit availability or proof-of-concept status is provided in the bundle.

Researcher notes

There is an evidence inconsistency: the description says The Mounty through version 1.1 is affected, while the affected array lists version “0” with defaultStatus “unaffected.” Use the narrative description and Patchstack reference as leads, then verify with vendor records before final scoping.

Mitigation direction

  • Identify whether any WordPress sites use The Mounty theme version 1.1 or earlier.
  • Check AncoraThemes and Patchstack guidance for a fixed version or official workaround.
  • If no fix is available, consider replacing or disabling the theme after business impact review.
  • Restrict administrative access and monitor suspicious requests to affected WordPress sites.

Validation and detection

  • Inventory installed WordPress themes across production, staging, and archived sites.
  • Confirm The Mounty theme version from WordPress administration or asset records.
  • Compare findings against the CVE description: affected through version 1.1.
  • Review web logs for unusual requests targeting theme files or include parameters.
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-22415 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-22415Attack 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
AncoraThemesThe Mountythe-mounty, 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.