CVE-2026-39566
Information Exposure in DirectoryPress β€ 3.6.26 Allows Sensitive Data Leak
Publication date: 2026-04-08
Last updated on: 2026-04-29
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| designinvento | directorypress | to 3.6.26 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-497 | The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-39566 is a vulnerability in the WordPress DirectoryPress Plugin versions up to and including 3.6.26. It is classified as a Sensitive Data Exposure issue that allows unauthenticated attackers to access sensitive system information that is normally restricted to regular users.
This exposure of embedded sensitive data can potentially enable attackers to exploit other weaknesses in the system. The vulnerability falls under the OWASP Top 10 category A3: Sensitive Data Exposure and requires no authentication to exploit.
How can this vulnerability impact me? :
The impact of this vulnerability is considered low severity with a CVSS score of 4.3, and exploitation is unlikely. However, it allows unauthorized attackers to retrieve sensitive information, which could be used to facilitate further attacks on the system.
Such vulnerabilities are often targeted in mass-exploit campaigns affecting many websites regardless of their popularity or traffic, increasing the risk of widespread compromise.
Users of the DirectoryPress Plugin are strongly advised to update to version 3.6.27 or later to mitigate this risk.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability affects DirectoryPress Plugin versions up to and including 3.6.26.
Users are strongly advised to update the DirectoryPress Plugin to version 3.6.27 or later to mitigate the risk.
Patchstack offers mitigation solutions including auto-updates specifically for vulnerable plugins.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to access sensitive information that is normally restricted to regular users, which constitutes Sensitive Data Exposure.
Exposure of sensitive data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access.
Although the impact is considered low severity and exploitation is unlikely, the presence of such a vulnerability increases the risk of data breaches, potentially affecting compliance with these standards.
Mitigation by updating to the patched version (3.6.27 or later) is strongly advised to reduce the risk and help maintain compliance.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability allows unauthenticated attackers to access sensitive information from the DirectoryPress WordPress plugin versions up to 3.6.26. Detection typically involves checking the plugin version and monitoring for unauthorized access attempts to sensitive data endpoints.
To detect if your system is vulnerable, first identify if the DirectoryPress plugin is installed and its version is 3.6.26 or lower.
- Use WP-CLI to check the plugin version: wp plugin list | grep directorypress
- Check the plugin version in the WordPress admin dashboard under Plugins.
To detect exploitation attempts or sensitive data exposure, monitor web server logs for unusual or unauthorized requests targeting DirectoryPress plugin endpoints that may reveal embedded sensitive data.
- Use grep or similar tools to search logs for suspicious requests: grep -i 'directorypress' /var/log/apache2/access.log
- Look for HTTP requests that do not require authentication but return sensitive data.
Ultimately, the best mitigation is to update the DirectoryPress plugin to version 3.6.27 or later.