What is the CVSS score of CVE-2026-57805?

CVE-2026-57805 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.5%.

How to fix or mitigate CVE-2026-57805?

Within 24 hours, inventory all WordPress installations across your infrastructure to identify any deployment of the Tonda theme through version 2.5 and document systems requiring immediate remediation. Within 7 days, remove the affected theme from all production environments; if replacement is not immediately feasible, apply filesystem-level hardening by restricting read access to wp-config.php, .env files, and sensitive log directories to only the web server process, deploy WAF rules to block directory traversal and arbitrary file inclusion patterns, and audit user permissions to revoke publishing capabilities from non-administrative accounts. Within 30 days, deploy a vetted replacement theme, establish ongoing monitoring of WordPress security advisories and Patchstack vulnerability feeds for any future Tonda theme patches, and complete a privileged access review to ensure user capability assignments align with business roles.

Tonda Theme CVE-2026-57805

EUVD-2026-43421 HIGH

PHP Remote File Inclusion (CWE-98)

2026-07-13 Patchstack

PHP WordPress Information Disclosure LFI Tonda Wordpress Theme Select Themes

7.5

CVSS 3.1 · Vendor: Patchstack

View

Attack ChainAIDerived

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

Access

Obtain low-privilege WordPress account
Delivery

Identify vulnerable Tonda include parameter
Exploit

Craft path-traversal/LFI payload
Execution

PHP include loads target local file
Persist

Disclose wp-config.php / secrets
Impact

Optional log poisoning to code execution

Vulnerability Assessment

Weakness	CWE CWE-98 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. Sign in to read
Exploitation Conditions	Exploitation requires an authenticated WordPress session with at least low privileges (CVSS PR:L) on a site running the Tonda theme version 2.5 or earlier, and the attacker must reach the specific theme code path that passes user-influenced input into a PHP include/require statement. The attack is network-reachable with no user interaction (AV:N/UI:N) but is rated high-complexity (AC:H), meaning specific non-default conditions or non-trivial payload crafting are needed rather than a trivial one-shot request. Limiting factors: the account requirement blocks purely anonymous attackers (except where open registration is on), and only the vulnerable Tonda theme deployments are in scope.
Impact	The provided CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H = 7.5) describes a network-reachable but higher-complexity flaw requiring some authentication (PR:L). Per the precision rules PR:L confirms this is an authenticated issue, not unauthenticated, which meaningfully limits mass exploitation to attackers who already hold a WordPress account (e.g., subscriber/contributor) or can obtain one where open registration is enabled. AC:H indicates non-trivial conditions must be met, further lowering drive-by risk. No EPSS score was provided and the CVE is absent from CISA KEV, and no POC was referenced - so real-world exploitation pressure appears low-to-moderate despite the High CVSS. Note a signal tension: the vector rates I:H and A:H, but the vendor tags label this "Information Disclosure / LFI," which is primarily a confidentiality impact; the High integrity/availability scores likely reflect worst-case LFI-to-RCE potential (log poisoning) rather than confirmed direct write/DoS - verify with the Patchstack advisory before treating I:H/A:H as certain.
Exploit ScenarioDerived	An attacker who has registered or obtained a low-privileged WordPress account submits a crafted request to a Tonda theme endpoint (e.g., a template/layout parameter) that manipulates a PHP include path to point at a local file such as ../../../../wp-config.php, retrieving database credentials and secret keys. With additional effort meeting the higher-complexity conditions (AC:H), the same primitive could be chained with log or session file poisoning to achieve code execution. No public proof-of-concept was referenced in the available data.

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 – Jul 13, 2026

Local File Inclusion in the Select-Themes "Tonda" WordPress theme (all versions through 2.5) lets an authenticated attacker with low privileges coerce a PHP include/require statement into loading arbitrary local files on the server. Tracked as CVE-2026-57805 (CWE-98) and reported by Patchstack, it carries a CVSS 7.5 rating and enables disclosure of sensitive files such as wp-config.php, with potential escalation to code execution via log/session poisoning. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

RemediationAI

No vendor-released patch version is identified at time of analysis; the input only confirms all versions up to and including 2.5 are affected, so monitor Select-Themes/Patchstack (https://patchstack.com/database/Wordpress/Theme/tonda/vulnerability/wordpress-tonda-theme-2-5-local-file-inclusion-vulnerability) and upgrade to the first release above 2.5 once published. Until a fix is available, apply compensating controls: use a WordPress WAF/virtual patch (Patchstack offers one) to block file-inclusion payloads and directory-traversal sequences against theme endpoints; tighten access by disabling open user registration and enforcing least-privilege roles since exploitation requires an authenticated account; and harden PHP by setting open_basedir and allow_url_include=Off to constrain which files the theme can include - noting open_basedir can break plugins that legitimately access paths outside the web root. If the theme is not essential, switch to a maintained theme as the most durable mitigation.

Affected VersionsENISA

Tonda 0 ≤2.5

Affected Packages

euvd tonda 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

The affected component is the Tonda commercial WordPress theme (CPE cpe:2.3:a:select-themes:tonda). The root cause is CWE-98, Improper Control of Filename for Include/Require Statement ('PHP Remote/Local File Inclusion'): a PHP include(), require(), include_once() or require_once() call builds its path from attacker-influenceable input (commonly a theme template, layout, or shortcode parameter) without a strict allowlist or path sanitization. Because WordPress themes execute within the full CMS context, an included file is parsed and run as PHP by the web server, meaning any file the PHP process can read may be exposed and, if attacker-controlled content can be written into an includable file, executed.

Know when PHP 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

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH

AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI 5.9 MEDIUM

Authenticated theme LFI (PR:L) reachable remotely but requiring specific conditions (AC:H); primary impact is file disclosure (C:H), with limited integrity via potential poisoning (I:L) and no direct availability impact (A:N).

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

4.0 AV:N/AC:H/AT:N/PR:L/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

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

DescriptionCVE.org

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Select-Themes Tonda tonda allows PHP Local File Inclusion.This issue affects Tonda: from n/a through <= 2.5.

Articles & Coverage 1

News 6 New PHP Vulnerabilities - 6 High Severity, No POC Available Jul 13, 2026

Executive ViewAI

Why It Matters

The Select-Themes 'Tonda' WordPress theme (all versions through 2.5) contains a local file inclusion vulnerability requiring authenticated access that allows low-privilege users to expose sensitive server files including wp-config.php and escalate privileges through log poisoning. Any WordPress installation running this freely distributed theme faces immediate risk of configuration disclosure and potential remote code execution through compromised or malicious user accounts. The vulnerability's reliance on existing authentication, combined with its wide deployment in WordPress ecosystems, creates a material risk for internal threat scenarios.

Business Impact: High

Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include immediate theme removal from production; web application firewall rules blocking suspicious file inclusion patterns and traversal sequences (../../../, encoded equivalents); filesystem permission hardening restricting access to wp-config.php and sensitive logs to web server process only; user permission audit to eliminate unnecessary publishing rights for low-privilege accounts; continuous monitoring of file access logs for inclusion attack attempts; and evaluation of dedicated WAF solutions with parameter-based file inclusion detection.

Threat Intelligence Overview

EPSS Score

0.5%

Top 61% exploitable

Prevalence

Rare

niche commercial WordPress theme from a single vendor, small install base

Data Quality

4 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS

Vulnrichment

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

Human Impact

High

Technical Impact

Total

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Local File Inclusion HIGH

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 MEDIUM

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