Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2019-25779 Overview
CVE-2019-25779 is a local file disclosure vulnerability in the WooThemes Diarise WordPress theme through version 1.5.9. The flaw resides in download.php, which accepts a user-supplied calendar parameter without proper validation. Unauthenticated attackers can submit GET requests containing file:// scheme paths to retrieve arbitrary files from the underlying server. Sensitive files such as /etc/passwd, WordPress configuration files, and application credentials become accessible over the network. The Shadowserver Foundation first observed active exploitation attempts targeting this issue on 2023-10-19. The vulnerability is tracked under CWE-22: Improper Limitation of a Pathname to a Restricted Directory.
Critical Impact
Unauthenticated remote attackers can read arbitrary files on the server, exposing credentials, configuration data, and system files that enable further compromise.
Affected Products
- WooThemes Diarise WordPress theme, all versions through 1.5.9
- WordPress installations with the vulnerable download.php endpoint exposed
- Any site using the theme's calendar export functionality
Discovery Timeline
- 2023-10-19 - Exploitation evidence first observed by the Shadowserver Foundation
- 2026-10-22 - CVE-2019-25779 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2019-25779
Vulnerability Analysis
The Diarise theme ships a download.php script intended to deliver calendar files to visitors. The script reads the calendar GET parameter and passes it directly to a file-reading function without sanitization or scheme filtering. Because PHP stream wrappers are enabled by default, attackers can supply URIs beginning with file:// to force the script to read any file the web server process can access. The response returns the requested file contents to the attacker.
Attackers typically exfiltrate /etc/passwd to confirm the vulnerability, then pivot to higher-value targets such as wp-config.php to extract database credentials and WordPress authentication keys.
Root Cause
The root cause is improper limitation of a pathname to a restricted directory [CWE-22]. The download.php handler trusts the calendar request parameter as a legitimate file reference. It performs no allowlist validation, no path canonicalization, and no restriction on stream wrappers before invoking file I/O.
Attack Vector
Exploitation requires only network access to the vulnerable WordPress site. An attacker issues an HTTP GET request to the theme's download.php endpoint and sets the calendar parameter to a file:// URI pointing at the target file. No authentication, user interaction, or elevated privileges are required. See the VulnCheck Advisory for Diarise LFD and the GitHub Nuclei Template for LFI for request details and detection logic.
Detection Methods for CVE-2019-25779
Indicators of Compromise
- GET requests to any URI containing /diarise/ and download.php with a calendar= parameter
- Request parameters that include file://, ../, or absolute paths such as /etc/passwd or wp-config.php
- HTTP 200 responses from download.php returning non-calendar content types or plaintext system file contents
- Unusual outbound reads of sensitive paths originating from the web server process
Detection Strategies
- Deploy the Nuclei template for the Diarise LFI against public-facing WordPress assets
- Create WAF signatures matching download.php?calendar=file:// and similar path traversal patterns
- Inspect web server access logs for requests to the Diarise theme directory with suspicious query strings
Monitoring Recommendations
- Alert on web server reads of /etc/passwd, /etc/shadow, wp-config.php, and private key files
- Track successful HTTP 200 responses to download.php with response sizes inconsistent with calendar exports
- Correlate repeated calendar parameter requests from a single source IP as reconnaissance activity
How to Mitigate CVE-2019-25779
Immediate Actions Required
- Remove or disable the Diarise theme on all WordPress sites until a patched version is confirmed
- Block external access to the theme's download.php script at the web server or WAF layer
- Rotate any credentials, API tokens, and WordPress salts that may have been exposed through wp-config.php
- Audit web server logs since 2023-10-19 for exploitation attempts against the vulnerable endpoint
Patch Information
No vendor advisory or official patch is referenced in the available data. WooThemes Diarise is a legacy commercial WordPress theme, and administrators should treat it as unmaintained. Review the VulnCheck Advisory for Diarise LFD and the CXSecurity Issue WLB-2019050123 for additional context, and migrate to an actively maintained theme.
Workarounds
- Deny HTTP access to wp-content/themes/diarise/download.php using web server rules
- Disable the PHP allow_url_include directive and restrict allow_url_fopen to limit stream wrapper abuse
- Apply open_basedir restrictions to confine PHP file reads to the WordPress document root
- Place a WAF rule that rejects any request where the calendar parameter contains ://, .., or starts with /
# Example Apache configuration to block the vulnerable endpoint
<Files "download.php">
Require all denied
</Files>
# Example Nginx location block
location ~* /wp-content/themes/diarise/download\.php$ {
deny all;
return 403;
}
# PHP hardening in php.ini
allow_url_include = Off
allow_url_fopen = Off
open_basedir = /var/www/html
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

