Skip to main content

Gita Theme CVE-2025-69160

| EUVDEUVD-2025-210176 HIGH
PHP Remote File Inclusion (CWE-98)
2026-06-16 Patchstack
8.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site running Gita theme
  2. Delivery
    Craft HTTP request with file path parameter
  3. Exploit
    Trigger unsafe PHP include in theme
  4. Execution
    Read wp-config.php credentials and salts
  5. Persist
    Authenticate to WordPress admin or database
  6. Impact
    Achieve full site takeover

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Command and Control

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The target WordPress site must have the ThemeRex Gita theme installed and activated at version 1.11 or earlier, and the vulnerable theme endpoint that performs the unsafe PHP include must be reachable over HTTP/HTTPS by the attacker. No authentication and no user interaction are required (PR:N/UI:N), but the CVSS AC:H rating indicates the attacker must satisfy a non-trivial precondition - likely a specific request parameter, file path encoding, or theme configuration - that is not enumerated in the public Patchstack summary. Exploitation is limited to deployments still using Gita ≤1.11; sites that have switched themes, sites where the vulnerable include path is blocked by a WAF or open_basedir restriction, and hosts where the PHP process cannot read sensitive files are out of scope.

Impact

Signals are mixed. The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H scores 8.1 (High) and reflects an unauthenticated network-reachable issue with full CIA impact, but AC:H indicates non-trivial exploitation conditions that the public description does not enumerate. The advisory is not in CISA KEV, no EPSS score was provided in the input, and no SSVC decision data is available, so widespread automated exploitation cannot be confirmed. The C:H/I:H/A:H impact triad is unusually high for a pure LFI and likely assumes chained outcomes (credential disclosure leading to admin takeover or RCE via log/upload poisoning) rather than the read-only file exposure the CWE alone implies - defenders should treat this as a credible WordPress theme compromise vector but verify real impact against their deployment.

Exploit ScenarioDerived

A remote attacker scans the public internet for WordPress sites running the Gita theme, then issues a crafted HTTP request to a vulnerable Gita endpoint with a parameter pointing at /wp-config.php (or via path traversal to /etc/passwd), causing the theme to include and disclose the file contents. The attacker uses the recovered database credentials and authentication keys to forge admin sessions or pivot to the database, achieving full site takeover; no public exploit is identified at time of analysis but the CWE-98 pattern is well understood and trivially weaponized once the vulnerable parameter is known.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 16, 2026

Unauthenticated local file inclusion in the ThemeRex Gita WordPress theme versions 1.11 and earlier allows remote attackers to include arbitrary local files via a PHP file-inclusion weakness (CWE-98), potentially exposing wp-config.php credentials and enabling further compromise. No public exploit identified at time of analysis, but the vulnerability is network-reachable without authentication and has been disclosed by Patchstack with a CVSS 3.1 base score of 8.1.

RemediationAI

No vendor-released patched version is identified in the available data, so administrators should consult the Patchstack advisory (https://patchstack.com/database/wordpress/theme/gita/vulnerability/wordpress-gita-theme-1-11-local-file-inclusion-vulnerability) and the ThemeRex vendor portal for a fixed release above 1.11 and upgrade immediately when available. Until a patched version is confirmed, compensating controls include deactivating and removing the Gita theme in favor of an unaffected theme (which will break the current site appearance), placing the site behind a WAF rule that blocks path-traversal sequences (../, encoded variants, php://, file://) and known WordPress LFI parameter patterns (trade-off: may break legitimate template requests and requires tuning), restricting filesystem permissions so the PHP process cannot read wp-config.php beyond what WordPress needs, rotating database credentials and WordPress salts in case prior exfiltration occurred, and monitoring web server logs for anomalous GET parameters resolving to PHP paths.

Affected VersionsENISA

Gita n/a ≤1.11

Affected Packages

euvd gita no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Gita is a commercial WordPress theme distributed by ThemeRex (CPE cpe:2.3:a:themerex:gita). The root cause is CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), commonly known as PHP Remote/Local File Inclusion. This class of bug arises when user-controlled input reaches a PHP include(), require(), include_once(), or require_once() call without strict allowlisting, letting attackers traverse the filesystem and include arbitrary local PHP files - frequently abused in WordPress themes that load template fragments based on request parameters. Successful inclusion of files such as wp-config.php discloses database credentials and authentication salts, and inclusion of attacker-controllable files (uploads, log files) can escalate LFI into code execution.

Know when Gita gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 6.5 MEDIUM

Unauthenticated network LFI with AC:H per reporter; primary impact is file disclosure (C:H), limited integrity via log/credential abuse (I:L), no direct availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated Local File Inclusion in Gita <= 1.11 versions.

Executive ViewAI

Why It Matters

The ThemeRex Gita WordPress theme (versions 1.11 and earlier) contains an unauthenticated file-inclusion vulnerability allowing remote attackers to access website configuration files containing database credentials and sensitive application secrets. Organizations using this theme face immediate risk of credential theft, unauthorized database access, and potential data breach or full website compromise.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Immediately deactivate the vulnerable theme; (2) Deploy Web Application Firewall blocking path traversal patterns (../, file://, etc.); (3) Restrict file permissions on wp-config.php to web server process only; (4) Enable and monitor web server access logs for file inclusion exploitation attempts; (5) Deploy WordPress hardening plugin (Wordfence, Sucuri) to add request-level filtering; (6) Disable PHP error reporting to prevent information disclosure.

Threat Intelligence Overview

EPSS Score
0.5%
Top 63% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy