Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13920: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in wpdirectorykit WP Directory Kit

0
Medium
VulnerabilityCVE-2025-13920cvecve-2025-13920cwe-200
Published: Sat Jan 24 2026 (01/24/2026, 12:27:15 UTC)
Source: CVE Database V5
Vendor/Project: wpdirectorykit
Product: WP Directory Kit

Description

CVE-2025-13920 is a medium severity vulnerability in the WP Directory Kit WordPress plugin (up to version 1. 4. 9) that allows unauthenticated attackers to extract email addresses of users assigned Directory Kit-specific roles via the wdk_public_action AJAX handler. This exposure of sensitive information does not require authentication or user interaction and impacts confidentiality but not integrity or availability. The vulnerability has a CVSS score of 5. 3, reflecting its moderate risk. No known exploits are currently reported in the wild. European organizations using this plugin, especially those with public-facing WordPress sites leveraging Directory Kit roles, are at risk of user email leakage, which could facilitate phishing or targeted social engineering. Mitigation involves updating the plugin once a patch is available or implementing access controls on the AJAX handler to restrict unauthenticated access. Countries with high WordPress adoption and significant use of Directory Kit, such as Germany, the UK, France, and the Netherlands, are most likely affected.

AI-Powered Analysis

AILast updated: 01/24/2026, 13:05:29 UTC

Technical Analysis

The WP Directory Kit plugin for WordPress, widely used to manage user directories with specialized roles, contains a vulnerability identified as CVE-2025-13920. This vulnerability arises from the wdk_public_action AJAX handler, which improperly exposes sensitive information—specifically, email addresses of users assigned Directory Kit-specific roles—to unauthenticated attackers. The flaw exists in all versions up to and including 1.4.9. Because the AJAX handler does not require authentication or user interaction, an attacker can remotely query this endpoint to harvest email addresses without any credentials. This constitutes a CWE-200 type vulnerability, indicating exposure of sensitive information to unauthorized actors. The CVSS v3.1 base score of 5.3 reflects a medium severity, driven by the network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). The impact is limited to confidentiality (C:L), with no effect on integrity or availability. Although no exploits have been reported in the wild, the vulnerability poses a risk of enabling phishing campaigns or other social engineering attacks by leaking user contact information. The plugin’s widespread use in WordPress sites that maintain user directories with specialized roles increases the potential attack surface. The vulnerability was published on January 24, 2026, and no official patches or mitigations have been linked yet, necessitating proactive defensive measures.

Potential Impact

For European organizations, the exposure of user email addresses can lead to increased phishing and spear-phishing attacks, potentially compromising user accounts or leading to credential theft. Organizations relying on WP Directory Kit for managing internal or external user directories may inadvertently leak sensitive contact information, undermining privacy compliance obligations such as GDPR. While the vulnerability does not directly affect system integrity or availability, the indirect consequences of successful phishing attacks could be severe, including unauthorized access, data breaches, and reputational damage. Public-facing WordPress sites with Directory Kit roles are particularly vulnerable, as attackers can easily enumerate email addresses without authentication. This risk is heightened in sectors with sensitive user data or critical communications, such as government, education, and healthcare institutions prevalent in Europe. The lack of known exploits in the wild suggests a window of opportunity for defenders to remediate before widespread abuse occurs.

Mitigation Recommendations

Immediate mitigation steps include restricting access to the wdk_public_action AJAX handler by implementing server-side access controls such as IP whitelisting or authentication requirements. Web application firewalls (WAFs) can be configured to detect and block suspicious requests targeting this endpoint. Organizations should monitor web server logs for unusual or repeated access attempts to the AJAX handler and alert on patterns indicative of enumeration. Until an official patch is released, disabling or removing the WP Directory Kit plugin may be necessary if the exposure risk outweighs its utility. Site administrators should also review user role assignments to minimize exposure of sensitive roles and consider obfuscating or limiting email address visibility in the directory. Once a patch is available, prompt updating of the plugin is critical. Additionally, educating users about phishing risks and implementing multi-factor authentication can reduce the impact of any compromised credentials resulting from this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-02T18:58:08.690Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6974c0304623b1157cb57048

Added to database: 1/24/2026, 12:50:56 PM

Last enriched: 1/24/2026, 1:05:29 PM

Last updated: 1/24/2026, 4:34:18 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats