CVE-2026-57795
Deferred Deferred - Pending Action

PHP Local File Inclusion in Kitchor

Vulnerability report for CVE-2026-57795, 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 themelexus Kitchor kitchor allows PHP Local File Inclusion.This issue affects Kitchor: from n/a through <= 1.4.3.

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
themelexus kitchor to 1.4.3 (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-57795 is a Local File Inclusion (LFI) vulnerability in the WordPress Kitchor Theme, versions 1.4.3 and below. This flaw allows attackers to include and display local files from the target website by exploiting improper control of filenames in PHP include/require statements.

If exploited, an attacker could access sensitive files on the server, such as configuration files or database credentials, depending on the server's configuration.

This vulnerability is classified under the OWASP Top 10 category A3: Injection and has a CVSS v3.1 base score of 7.5, indicating a significant security risk.

Detection Guidance

This vulnerability involves Local File Inclusion (LFI) in the WordPress Kitchor Theme, which allows attackers to include and display local files from the target website.

To detect this vulnerability, you can look for unusual HTTP requests attempting to include local files via URL parameters related to the theme's include or require statements.

Common detection methods include monitoring web server logs for suspicious requests containing file path traversal patterns such as "../" or attempts to access sensitive files like "/etc/passwd".

Example commands to search for such patterns in web server logs (assuming Apache logs):

  • grep -i 'kitchor' /var/log/apache2/access.log | grep -E '\.\./|etc/passwd'
  • grep -E 'include|require' /var/log/apache2/access.log | grep '\.\./'

Additionally, vulnerability scanners or web application scanners that support LFI detection can be used to test the site.

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive information by allowing attackers to include and view local files on the affected website.

Such exposure could reveal critical data like database credentials, configuration files, or other sensitive information stored on the server.

The impact includes potential data breaches, loss of confidentiality, and increased risk of further exploitation or compromise of the website.

Compliance Impact

This vulnerability, a Local File Inclusion (LFI) in the Kitchor theme, can significantly impact compliance with standards and regulations like GDPR and HIPAA due to its potential to expose sensitive data.

  • GDPR: If the vulnerability allows unauthorized access to personally identifiable information (PII) stored in local files (e.g., configuration files containing user data), it could lead to a data breach. Under GDPR, organizations must protect PII and report breaches within 72 hours. Failure to do so may result in fines up to 4% of global revenue or €20 million, whichever is higher.
  • HIPAA: For organizations handling protected health information (PHI), this vulnerability could lead to unauthorized access to PHI if local files containing such data are exposed. HIPAA requires strict safeguards for PHI, and a breach could result in penalties ranging from $100 to $50,000 per violation, with a maximum of $1.5 million per year for identical violations.
  • General compliance risks: The vulnerability is classified under OWASP Top 10 A3: Injection, which is a critical security risk. Many compliance frameworks (e.g., PCI DSS, ISO 27001) require mitigation of injection vulnerabilities. Failure to address this issue could lead to non-compliance and potential legal or financial consequences.

Since there is no official patch available, organizations must take immediate action to mitigate the risk, such as updating the theme, implementing additional security controls, or seeking assistance from security professionals to avoid compliance violations.

Mitigation Strategies

Immediate mitigation steps include updating the WordPress Kitchor Theme to a non-vulnerable version if available.

Since there is currently no official patch available for this vulnerability, it is recommended to seek assistance from your hosting provider or a web developer to apply temporary fixes or workarounds.

Other mitigation measures include disabling or restricting the vulnerable theme until a patch is released, and implementing web application firewall (WAF) rules to block suspicious requests attempting Local File Inclusion.

Regularly monitor your website and server logs for signs of exploitation and consider restricting file permissions to limit the impact of potential attacks.

Chat Assistant

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

EPSS Chart