CVE-2026-28043
Local File Inclusion in Healer WordPress Theme Allows Code Execution
Publication date: 2026-03-05
Last updated on: 2026-03-06
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| themerex | healer | to 1.0.0 (inc) |
Helpful Resources
Exploitability
| 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?
[{'type': 'paragraph', 'content': 'CVE-2026-28043 is a Local File Inclusion (LFI) vulnerability in the WordPress theme "Healer - Doctor, Clinic & Medical" versions up to and including 1.0.0.'}, {'type': 'paragraph', 'content': 'This vulnerability allows unauthenticated attackers to include and display local files from the target website by exploiting improper control of filename parameters in PHP include/require statements.'}, {'type': 'paragraph', 'content': 'As a result, attackers can potentially access sensitive information stored on the server.'}] [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to exposure of sensitive information such as database credentials.
Depending on the server configuration, attackers could achieve complete database takeover.
This represents a critical risk to the security and integrity of the affected website.
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': 'This vulnerability allows unauthenticated attackers to include and display local files from the target website, which may be detected by monitoring for suspicious HTTP requests attempting to exploit Local File Inclusion (LFI) patterns.'}, {'type': 'paragraph', 'content': 'Common detection methods include inspecting web server logs for requests containing suspicious parameters that reference local files, such as attempts to include files via URL parameters.'}, {'type': 'list_item', 'content': "Use tools like grep to search web server access logs for suspicious patterns, e.g., grep -i 'include' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': 'Look for requests containing directory traversal sequences (../) or references to sensitive files like /etc/passwd.'}, {'type': 'list_item', 'content': 'Use web application scanners or vulnerability scanners that can detect Local File Inclusion vulnerabilities.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Since no official patch is currently available for this vulnerability, immediate mitigation should focus on applying the Patchstack mitigation rule designed to block attacks targeting this issue.
Users are strongly advised to implement Patchstack’s mitigation measures immediately to protect their websites from exploitation.
Additional general mitigation steps include restricting access to sensitive files, disabling unnecessary PHP functions, and monitoring for suspicious activity.
Consider temporarily disabling or replacing the vulnerable theme until an official patch is released.