CVE-2025-68887

7.1

CMSJunkie · WP-BusinessDirectory

The WP-BusinessDirectory plugin for WordPress is vulnerable to reflected cross-site scripting (XSS) due to improper neutralization of user-supplied input during web page generation.

Executive summary

A reflected cross-site scripting vulnerability in the CMSJunkie WP-BusinessDirectory plugin allows unauthenticated attackers to execute malicious scripts in a user's browser.

Vulnerability

This vulnerability is a reflected cross-site scripting (XSS) flaw, categorized as CWE-79, which occurs because the application fails to properly sanitize input before rendering it in the browser. The attack vector is network-based and requires no authentication, though it does require user interaction to trigger the malicious payload.

Business impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of an unsuspecting user's session. This can lead to session hijacking, unauthorized actions performed on behalf of the user, or the exfiltration of sensitive information, potentially impacting the overall security and integrity of the WordPress site. The CVSS score of 7.1 reflects the high risk posed by potential unauthorized access and interaction with authenticated sessions.

Remediation

Immediate Action: As no specific patch version is currently confirmed, administrators should immediately deactivate and remove the WP-BusinessDirectory plugin until a secure update is released by CMSJunkie.

Proactive Monitoring: Security teams should monitor web server access logs for suspicious URL parameters containing encoded scripts or unusual request patterns targeting the plugin directory.

Compensating Controls: Deploy a Web Application Firewall (WAF) with robust XSS protection rules to detect and block malicious payloads directed at the vulnerable application endpoints.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the potential for session compromise and the lack of a verified patch, the risk to the environment is significant. Administrators must prioritize the removal or containment of the affected plugin to prevent exploitation. Continue to monitor official vendor channels for the release of a security update and only re-enable the functionality once the plugin has been patched to a version beyond 4.0.1.

More CMSJunkie CVEs

Sources

Originally found and disclosed by Nguyen Xuan Chien | Patchstack Bug Bounty Program, per the CVE Program record.