GetYourGuide Ticketing <= 1.0.2 - Authenticated (Admin+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.0.3
- Affected Plugin
- GetYourGuide Ticketing
- Affected Version
<= 1.0.2- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-3609
At a glance
CVE-2022-3609 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the GetYourGuide Ticketing WordPress plugin, affecting versions <= 1.0.2. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.0.3; sites on affected versions should update now. Disclosed September 2022, reported by Mariam Tariq.
Vulnerability Overview
The GetYourGuide Ticketing plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘partner_hash’ parameter in versions up to, and including, 1.0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
GetYourGuide Ticketing <= 1.0.2 carries this weakness at partner_hash, and reaching it takes an account at Admin level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For GetYourGuide Ticketing the fix is 1.0.3: builds <= 1.0.2 are affected, anything from 1.0.3 onward is not.
Remediation
Update to version 1.0.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GetYourGuide Ticketing 1.0.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C