CVE-2026-57792
Deferred Deferred - Pending Action

PHP Local File Inclusion in Mikado-Themes Dør

Vulnerability report for CVE-2026-57792, 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 Mikado-Themes Dør dor allows PHP Local File Inclusion.This issue affects Dør: from n/a through <= 2.4.1.

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
mikado-themes dor to 2.4.1 (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

This vulnerability is an improper control of filename for include/require statements in a PHP program, specifically in Mikado-Themes Dør dor. It is a PHP Local File Inclusion (LFI) vulnerability that affects versions up to and including 2.4.1. This means that an attacker can manipulate the filename parameter used in include or require statements to include unintended files on the server.

Detection Guidance

Detecting this PHP Remote File Inclusion (RFI) or Local File Inclusion (LFI) vulnerability in Mikado-Themes Dør requires checking for vulnerable versions of the software and inspecting web application behavior.

  • Identify if the Mikado-Themes Dør plugin is installed and its version. The vulnerability affects versions up to and including 2.4.1. Check the plugin directory or WordPress admin panel for version details.
  • Look for suspicious include/require statements in PHP files that dynamically include files based on user input. Example commands to search for vulnerable patterns in PHP files:
  • grep -r "include(" /path/to/wordpress/wp-content/plugins/dor/
  • grep -r "require(" /path/to/wordpress/wp-content/plugins/dor/
  • grep -r "include_once(" /path/to/wordpress/wp-content/plugins/dor/
  • grep -r "require_once(" /path/to/wordpress/wp-content/plugins/dor/
  • Check web server logs for unusual requests containing patterns like "?file=", "?page=", or other parameters that might be used to exploit file inclusion vulnerabilities.
  • Use a web application scanner like OWASP ZAP or Burp Suite to test for RFI/LFI vulnerabilities by sending crafted requests to the application.

Note: Manual inspection is required to confirm the presence of the vulnerability, as automated tools may not detect all cases.

Impact Analysis

The vulnerability has a high severity with a CVSS base score of 7.5. It can lead to significant impacts including confidentiality, integrity, and availability being compromised. An attacker with low privileges and no user interaction required can exploit this vulnerability remotely, potentially gaining access to sensitive files, executing arbitrary code, or causing denial of service.

Compliance Impact

This vulnerability, a PHP Remote File Inclusion (RFI) and Local File Inclusion (LFI), can significantly impact compliance with standards and regulations like GDPR and HIPAA due to its potential to expose sensitive data or allow unauthorized code execution.

  • GDPR: If the affected system processes personal data of EU citizens, this vulnerability could lead to unauthorized access or disclosure of such data, violating GDPR's requirements for data protection and confidentiality (Articles 5, 25, and 32). A breach could result in hefty fines and legal consequences.
  • HIPAA: For systems handling protected health information (PHI), this vulnerability could enable attackers to access or manipulate sensitive patient data, violating HIPAA's Security Rule (45 CFR Part 164, Subpart C). This could lead to non-compliance penalties and reputational damage.
  • Other standards: The vulnerability may also conflict with frameworks like ISO 27001, which mandates secure handling of information assets, or PCI DSS if the system processes payment card data, as it could expose cardholder information to unauthorized parties.

The CVSS score of 7.5 (High) indicates a severe risk, further emphasizing the need for immediate remediation to maintain compliance with these regulations.

Mitigation Strategies

To mitigate this vulnerability, follow these immediate steps:

  • Upgrade Mikado-Themes Dør to the latest version if a patch is available. Since the vulnerability affects versions up to and including 2.4.1, check for updates from the vendor or official sources.
  • If no patch is available, consider disabling or removing the vulnerable plugin until a fix is released.
  • Implement input validation and sanitization for all file inclusion operations in the application. Ensure user-supplied input is not directly used in include/require statements.
  • Restrict file inclusion to a whitelist of allowed files or directories to prevent unauthorized access.
  • Disable remote file inclusion by setting "allow_url_include" to "Off" in the PHP configuration (php.ini).
  • Monitor web server logs for signs of exploitation attempts, such as requests containing suspicious file paths or remote URLs.
  • Consider deploying a web application firewall (WAF) to block known attack patterns related to RFI/LFI vulnerabilities.

Chat Assistant

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

EPSS Chart