CVE-2025-68543
Awaiting Analysis Awaiting Analysis - Queue
Local File Inclusion in Diza PHP Plugin Allows Code Execution

Publication date: 2026-02-20

Last updated on: 2026-02-24

Assigner: Patchstack

Description
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in thembay Diza diza allows PHP Local File Inclusion.This issue affects Diza: from n/a through <= 1.3.15.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-20
Last Modified
2026-02-24
Generated
2026-05-27
AI Q&A
2026-02-20
EPSS Evaluated
2026-05-25
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
thembay diza From 1.0 (inc) to 1.3.15 (inc)
thembay diza to 1.3.15 (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 Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-68543 is a Local File Inclusion (LFI) vulnerability in the WordPress Diza Theme versions up to and including 1.3.15. It allows an unauthenticated attacker to include and display local files from the target website. This happens due to improper control of the filename used in include/require statements in the PHP program.

Because of this, sensitive information such as database credentials can be exposed. The vulnerability is classified under the OWASP Top 10 category A3: Injection and has a high severity CVSS score of 8.1.


How can this vulnerability impact me? :

[{'type': 'paragraph', 'content': "This vulnerability can have serious impacts including exposure of sensitive information like database credentials. An attacker exploiting this vulnerability could potentially take over the entire database depending on the website's configuration."}, {'type': 'paragraph', 'content': 'Since the vulnerability requires no privileges to exploit, it is particularly dangerous and can lead to a complete compromise of the affected website.'}] [1]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'CVE-2025-68543 is a Local File Inclusion (LFI) vulnerability in the WordPress Diza Theme up to version 1.3.15 that allows unauthenticated attackers to include and display local files. Detection typically involves monitoring for suspicious HTTP requests attempting to include local files via the vulnerable theme.'}, {'type': 'paragraph', 'content': 'While specific commands are not provided in the resources, common detection methods include inspecting web server logs for requests containing suspicious parameters that attempt to include local files, such as those with directory traversal patterns or file inclusion keywords.'}, {'type': 'paragraph', 'content': 'For example, you can use commands like the following to search web server logs for potential exploitation attempts:'}, {'type': 'list_item', 'content': "grep -i 'include' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "grep -E '\\.\\./|\\binclude\\b' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "tail -f /var/log/apache2/access.log | grep 'diza'"}, {'type': 'paragraph', 'content': 'Additionally, using web application firewalls (WAFs) or automated vulnerability scanners that support detection of LFI vulnerabilities in WordPress themes can help identify exploitation attempts.'}] [1]


What immediate steps should I take to mitigate this vulnerability?

The most immediate and effective mitigation step is to update the WordPress Diza Theme to version 1.3.16 or later, where the vulnerability has been patched.

Until the update can be applied, it is strongly advised to implement mitigation rules to block attacks targeting this vulnerability. Patchstack provides such mitigation rules to protect sites from exploitation.

Additional steps include:

  • Deploy a web application firewall (WAF) with rules to detect and block Local File Inclusion attempts.
  • Monitor web server logs for suspicious requests attempting file inclusion.
  • Restrict file permissions and access to sensitive files on the server to minimize impact.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart