CVE-2025-6200: CWE-79 Cross-Site Scripting (XSS) in GeoDirectory
The GeoDirectory WordPress plugin before 2.8.120 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.
AI Analysis
Technical Summary
CVE-2025-6200 is a Stored Cross-Site Scripting (XSS) vulnerability identified in the GeoDirectory WordPress plugin prior to version 2.8.120. The root cause is the failure to properly validate and escape certain shortcode attributes before outputting them in pages or posts where the shortcode is embedded. This flaw allows users with contributor-level or higher privileges to inject malicious JavaScript code that is stored persistently and executed when other users view the affected content. The vulnerability leverages the plugin’s shortcode processing mechanism, which dynamically renders user-supplied attributes without sufficient sanitization. Because contributors can create or edit posts containing shortcodes, they can embed payloads that execute in the context of site visitors or administrators, potentially leading to session hijacking, privilege escalation, or defacement. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L) indicates network attack vector, low attack complexity, required privileges at the contributor level, required user interaction, and a scope change affecting confidentiality, integrity, and availability at a limited level. Although no public exploits are reported yet, the vulnerability poses a moderate risk to WordPress sites using GeoDirectory, especially those with multiple contributors. The vulnerability was publicly disclosed on July 11, 2025, and is tracked under CWE-79, a common category for XSS issues. The absence of patch links suggests that users should verify plugin updates or apply manual mitigations promptly.
Potential Impact
For European organizations, this vulnerability can lead to unauthorized script execution within their WordPress sites, compromising user sessions, leaking sensitive information, or defacing web content. Organizations relying on GeoDirectory for location-based services or directory listings may face reputational damage and operational disruption if attackers exploit this flaw to inject malicious content. The requirement for contributor-level privileges limits exploitation to insiders or compromised accounts, but many organizations allow multiple contributors, increasing risk. The partial impact on confidentiality, integrity, and availability means attackers could steal cookies, manipulate displayed data, or cause denial of service conditions. Given the widespread use of WordPress across Europe, especially in small and medium enterprises and public sector websites, the vulnerability could affect a broad range of sectors including tourism, real estate, and local government services that use GeoDirectory. Failure to remediate promptly could also increase the risk of chained attacks leveraging this XSS as an initial foothold.
Mitigation Recommendations
1. Immediately update the GeoDirectory plugin to version 2.8.120 or later once available to ensure the vulnerability is patched. 2. Until an official patch is released, restrict contributor and higher roles from adding or editing shortcodes containing user-supplied attributes. 3. Implement strict input validation and output escaping for shortcode attributes via custom filters or security plugins to sanitize inputs. 4. Enforce the principle of least privilege by reviewing and minimizing the number of users with contributor or higher roles. 5. Monitor logs and web traffic for unusual script injections or unexpected shortcode content changes. 6. Use Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected sites. 7. Educate content contributors about the risks of embedding untrusted code or shortcodes. 8. Regularly audit WordPress plugins and themes for updates and vulnerabilities. 9. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block XSS payloads targeting shortcode parameters. 10. Backup site data frequently to enable quick recovery in case of compromise.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-6200: CWE-79 Cross-Site Scripting (XSS) in GeoDirectory
Description
The GeoDirectory WordPress plugin before 2.8.120 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.
AI-Powered Analysis
Technical Analysis
CVE-2025-6200 is a Stored Cross-Site Scripting (XSS) vulnerability identified in the GeoDirectory WordPress plugin prior to version 2.8.120. The root cause is the failure to properly validate and escape certain shortcode attributes before outputting them in pages or posts where the shortcode is embedded. This flaw allows users with contributor-level or higher privileges to inject malicious JavaScript code that is stored persistently and executed when other users view the affected content. The vulnerability leverages the plugin’s shortcode processing mechanism, which dynamically renders user-supplied attributes without sufficient sanitization. Because contributors can create or edit posts containing shortcodes, they can embed payloads that execute in the context of site visitors or administrators, potentially leading to session hijacking, privilege escalation, or defacement. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L) indicates network attack vector, low attack complexity, required privileges at the contributor level, required user interaction, and a scope change affecting confidentiality, integrity, and availability at a limited level. Although no public exploits are reported yet, the vulnerability poses a moderate risk to WordPress sites using GeoDirectory, especially those with multiple contributors. The vulnerability was publicly disclosed on July 11, 2025, and is tracked under CWE-79, a common category for XSS issues. The absence of patch links suggests that users should verify plugin updates or apply manual mitigations promptly.
Potential Impact
For European organizations, this vulnerability can lead to unauthorized script execution within their WordPress sites, compromising user sessions, leaking sensitive information, or defacing web content. Organizations relying on GeoDirectory for location-based services or directory listings may face reputational damage and operational disruption if attackers exploit this flaw to inject malicious content. The requirement for contributor-level privileges limits exploitation to insiders or compromised accounts, but many organizations allow multiple contributors, increasing risk. The partial impact on confidentiality, integrity, and availability means attackers could steal cookies, manipulate displayed data, or cause denial of service conditions. Given the widespread use of WordPress across Europe, especially in small and medium enterprises and public sector websites, the vulnerability could affect a broad range of sectors including tourism, real estate, and local government services that use GeoDirectory. Failure to remediate promptly could also increase the risk of chained attacks leveraging this XSS as an initial foothold.
Mitigation Recommendations
1. Immediately update the GeoDirectory plugin to version 2.8.120 or later once available to ensure the vulnerability is patched. 2. Until an official patch is released, restrict contributor and higher roles from adding or editing shortcodes containing user-supplied attributes. 3. Implement strict input validation and output escaping for shortcode attributes via custom filters or security plugins to sanitize inputs. 4. Enforce the principle of least privilege by reviewing and minimizing the number of users with contributor or higher roles. 5. Monitor logs and web traffic for unusual script injections or unexpected shortcode content changes. 6. Use Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected sites. 7. Educate content contributors about the risks of embedding untrusted code or shortcodes. 8. Regularly audit WordPress plugins and themes for updates and vulnerabilities. 9. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block XSS payloads targeting shortcode parameters. 10. Backup site data frequently to enable quick recovery in case of compromise.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- WPScan
- Date Reserved
- 2025-06-17T12:44:02.645Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68712038a83201eaacaf28dd
Added to database: 7/11/2025, 2:31:20 PM
Last enriched: 1/9/2026, 8:50:21 PM
Last updated: 1/10/2026, 10:13:50 PM
Views: 133
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0824: Cross Site Scripting in questdb ui
MediumCVE-2025-13393: CWE-918 Server-Side Request Forgery (SSRF) in marceljm Featured Image from URL (FIFU)
MediumCVE-2025-12379: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in averta Shortcodes and extra features for Phlox theme
MediumCVE-2026-0822: Heap-based Buffer Overflow in quickjs-ng quickjs
MediumCVE-2026-0821: Heap-based Buffer Overflow in quickjs-ng quickjs
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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.