CVE-2026-125805 in GeoDirectory Plugin
Summary
by MITRE • 11/15/2026
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in AyeCode Ltd GeoDirectory geodirectory allows Stored XSS.This issue affects GeoDirectory: from n/a through 2.8.204.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/15/2026
The identified security flaw represents a classic instance of Improper Neutralization of Input During Web Page Generation, commonly known as Cross-Site Scripting or XSS. Specifically, this vulnerability manifests as a Stored XSS within the GeoDirectory plugin developed by AyeCode Ltd. Unlike reflected XSS attacks where malicious scripts are executed immediately upon request processing, stored vulnerabilities persist on the target server because the injected payload is saved in databases or other storage mechanisms. This particular issue affects versions of GeoDirectory ranging from n/a through version 2.8.204, indicating a long-standing exposure for users who have not applied timely updates to their WordPress environments.
The technical root cause lies in the insufficient sanitization and validation of user-supplied input before it is rendered back into web pages without proper encoding. When an attacker submits malicious JavaScript code through any field that accepts free-form text within the GeoDirectory plugin, such as listing titles, descriptions, or custom fields, the application fails to neutralize special characters like angle brackets, quotes, and ampersands. Consequently, when other users visit the affected page, their browsers interpret the stored script as legitimate content rather than data. This allows the attacker's code to execute within the context of the victim’s browser session, leveraging the trust that the user has in the GeoDirectory application interface.
The operational impact of this vulnerability is severe due to its persistent nature and potential for widespread exploitation. Attackers can use stored XSS to steal sensitive information such as administrative cookies, session tokens, or authentication credentials by exfiltrating them to a remote server controlled by the attacker. Furthermore, it enables account takeover attacks where an adversary hijacks active sessions of site administrators or other privileged users. Beyond credential theft, this vulnerability facilitates phishing campaigns by allowing attackers to inject deceptive login forms or malicious content directly into legitimate pages, thereby deceiving unsuspecting visitors. It can also be used to deface websites, redirect traffic to malicious domains, or deploy further malware onto client machines through drive-by downloads if combined with other browser vulnerabilities.
From a classification perspective, this vulnerability aligns with CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). In the context of offensive security frameworks, it maps directly to MITRE ATT&CK technique T1059.007: Command and Control via Browser Proxy or T1189: Drive-by Client Compromise when used for initial access, though primarily it serves as a mechanism for persistent access and data exfiltration under techniques like T1005: Data from Local System or T1078: Valid Accounts if session hijacking is successful. The persistence of the payload means that remediation requires not only patching but also cleaning existing malicious entries in the database to prevent continued exploitation even after software updates are applied.
Mitigation strategies must focus on both immediate containment and long-term prevention. Organizations running affected versions of GeoDirectory should immediately upgrade to a patched version released by AyeCode Ltd, ensuring that all instances across their infrastructure are updated consistently. In addition to patching, implementing a Web Application Firewall can provide an additional layer of defense by filtering out malicious input patterns before they reach the application logic. Developers and administrators must also enforce strict Content Security Policy headers to restrict the execution of inline scripts and limit sources from which external resources can be loaded. Regular security audits and code reviews focusing on input validation and output encoding practices are essential to prevent similar vulnerabilities in future development cycles, ensuring that all user inputs are treated as untrusted data until explicitly validated against a whitelist of acceptable characters or formats.