CVE-2026-57805
Deferred Deferred - Pending Action

PHP Local File Inclusion in Tonda Theme

Vulnerability report for CVE-2026-57805, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Patchstack

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-08-02
AI Q&A
2026-07-13
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
select-themes tonda From 2.0 (inc) to 2.5 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-98 The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-57805 is a Local File Inclusion (LFI) vulnerability in the WordPress Tonda Theme versions 2.5 and below. It arises from improper control of filenames used in PHP include or require statements, allowing an attacker with contributor-level privileges to include local files from the target website.

This flaw can lead to exposure of sensitive data such as database credentials if the website's configuration permits it. The vulnerability is classified under the OWASP Top 10 category A3: Injection.

Detection Guidance

Detecting the Local File Inclusion (LFI) vulnerability in the Tonda theme (CVE-2026-57805) on your system or network involves checking for the presence of vulnerable versions of the theme and testing for the vulnerability. Below are some methods and commands to help identify this issue.

  • Check the installed version of the Tonda theme on your WordPress site. Navigate to the WordPress admin dashboard, go to 'Appearance' > 'Themes', and verify the version of the Tonda theme. If the version is 2.5 or below, the site is vulnerable.
  • Use a WordPress vulnerability scanner like WPScan to detect the vulnerability. Run the following command to scan your WordPress site for known vulnerabilities, including CVE-2026-57805:
  • wpscan --url <your-wordpress-site-url> --enumerate vp
  • Manually test for the LFI vulnerability by attempting to access local files through the theme's vulnerable endpoints. For example, you can use curl or a browser to send requests like:
  • curl 'http://<your-wordpress-site-url>/wp-content/themes/tonda/vulnerable-file.php?file=../../../../etc/passwd'
  • Replace 'vulnerable-file.php' with the actual vulnerable file or parameter in the Tonda theme. If the response includes the contents of the requested local file (e.g., /etc/passwd), the site is vulnerable.
  • Review server logs for suspicious requests targeting the Tonda theme. Look for patterns such as requests containing '../' or attempts to access sensitive files like '/etc/passwd', 'wp-config.php', or other configuration files.
  • Use network monitoring tools like Wireshark or tcpdump to capture and analyze HTTP traffic for unusual requests that may indicate exploitation attempts. Filter for requests to the Tonda theme directory or suspicious file inclusion patterns.
Impact Analysis

The vulnerability can allow attackers to include and access local files on the affected website, potentially exposing sensitive information like database credentials.

This can lead to a high impact on confidentiality, integrity, and availability of the affected system, as indicated by its CVSS score of 7.5.

However, the exploitability is considered limited and the vulnerability is currently unpatched.

Compliance Impact

This vulnerability, a Local File Inclusion (LFI) in the Tonda theme, can significantly impact compliance with standards and regulations like GDPR and HIPAA.

  • GDPR: The vulnerability may lead to unauthorized access to sensitive data, such as database credentials or personally identifiable information (PII). Under GDPR, organizations must protect personal data from unauthorized access or disclosure. If exploited, this flaw could result in a data breach, triggering mandatory reporting requirements and potential fines for non-compliance.
  • HIPAA: For organizations handling protected health information (PHI), this vulnerability could expose sensitive patient data. HIPAA requires strict safeguards to prevent unauthorized access to PHI. A successful exploit could violate the Security Rule, leading to penalties and corrective action plans.

Additionally, the vulnerability falls under OWASP Top 10 category A3: Injection, which is a critical security risk. Compliance frameworks often reference OWASP guidelines, and failing to address such risks may indicate inadequate security controls, further complicating compliance efforts.

Mitigation Strategies

Immediate action is recommended to mitigate this vulnerability.

  • Update the WordPress Tonda Theme to a version above 2.5 if available.
  • Seek assistance from your hosting provider or a developer to address the issue.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57805. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart