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-13525: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in listingthemes WP Directory Kit

0
Medium
VulnerabilityCVE-2025-13525cvecve-2025-13525cwe-79
Published: Thu Nov 27 2025 (11/27/2025, 05:31:56 UTC)
Source: CVE Database V5
Vendor/Project: listingthemes
Product: WP Directory Kit

Description

The WP Directory Kit plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'order_by' parameter in all versions up to, and including, 1.4.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

AI-Powered Analysis

AILast updated: 12/04/2025, 06:24:48 UTC

Technical Analysis

CVE-2025-13525 is a reflected Cross-Site Scripting vulnerability classified under CWE-79 found in the WP Directory Kit plugin for WordPress, versions up to and including 1.4.5. The vulnerability stems from insufficient input sanitization and output escaping of the 'order_by' parameter used in web page generation. This flaw allows unauthenticated attackers to craft malicious URLs containing JavaScript payloads that, when clicked by a victim, execute in the context of the vulnerable website. This can lead to theft of session cookies, defacement, or redirection to malicious sites, compromising user confidentiality and integrity. The CVSS v3.1 score of 6.1 reflects a medium severity with network attack vector, low attack complexity, no privileges required, but requiring user interaction. The scope is changed (S:C) because the vulnerability affects resources beyond the vulnerable component, potentially impacting user sessions. No known exploits have been reported in the wild yet, but the vulnerability is publicly disclosed and should be treated seriously. The plugin is widely used in WordPress sites that provide directory listings, often for small and medium enterprises, event listings, or local business directories. The lack of a patch at the time of disclosure necessitates interim mitigations such as web application firewall (WAF) rules or manual code fixes to sanitize and escape inputs properly.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to websites using the WP Directory Kit plugin, which may be common among SMEs and local service providers. Successful exploitation can lead to session hijacking, unauthorized actions on behalf of users, or phishing via script injection, undermining user trust and potentially leading to data breaches involving personal information. Although availability is not impacted, the confidentiality and integrity of user data and site content are at risk. This can result in reputational damage, regulatory non-compliance under GDPR due to compromised personal data, and financial losses from remediation and potential legal penalties. Public-facing directory sites are particularly vulnerable as they often have high user interaction and visibility. The medium severity score indicates that while the vulnerability is not trivial, it is exploitable remotely without authentication, increasing the attack surface. European organizations with significant online presence and customer interaction through WordPress sites should prioritize addressing this issue to prevent exploitation.

Mitigation Recommendations

1. Monitor the WP Directory Kit plugin vendor for an official patch and apply it immediately upon release. 2. Until a patch is available, implement Web Application Firewall (WAF) rules to detect and block malicious payloads targeting the 'order_by' parameter. 3. Conduct manual code review and apply input validation and output escaping on the 'order_by' parameter in the plugin code to neutralize potentially malicious input. 4. Educate users and administrators about the risks of clicking suspicious links, especially those containing unusual query parameters. 5. Employ Content Security Policy (CSP) headers to restrict script execution sources, mitigating the impact of injected scripts. 6. Regularly audit WordPress plugins for updates and vulnerabilities, and limit plugin usage to trusted and actively maintained components. 7. Use security plugins that can detect and block XSS attempts and anomalous behavior on WordPress sites. 8. Conduct penetration testing focusing on input validation and XSS vectors to identify similar issues proactively.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-21T19:45:44.250Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6927e4dfbdf69728cfe59424

Added to database: 11/27/2025, 5:42:55 AM

Last enriched: 12/4/2025, 6:24:48 AM

Last updated: 1/11/2026, 12:46:47 PM

Views: 61

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