Awesome Support <= 6.0.7 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 6.0.8
- Affected Plugin
- Awesome Support – WordPress HelpDesk & Support Plugin
- Affected Version
<= 6.0.7- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-38073
At a glance
CVE-2022-38073 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Awesome Support WordPress plugin, affecting versions <= 6.0.7. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.0.8; sites on affected versions should update now. Disclosed September 2022, reported by R3N0.
Vulnerability Overview
The Awesome Support plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 6.0.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Several vulnerabilities are present in this version of the plugin requiring different privilege levels.
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 privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Awesome Support <= 6.0.7 takes any authenticated account. 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 Awesome Support the fix is 6.0.8: builds <= 6.0.7 are affected, anything from 6.0.8 onward is not.
Remediation
Update to version 6.0.8, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Awesome Support: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Awesome Support 6.0.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.1CVE-2023-5354: Awesome Support <= 6.1.4 Reflected Cross-Site Scripting
CVE-2023-5354 - 6.1CVE-2021-36919: Awesome Support Reflected XSS
CVE-2021-36919 - 6.1CVE-2021-24435: Titan Framework <= (Various Versions) Reflected XSS
CVE-2021-24435 - 6.1CVE-2015-9317: Awesome Support – WordPress HelpDesk & Support XSS
CVE-2015-9317
Other vulnerabilities in Awesome Support – WordPress HelpDesk & Support Plugin
- 8.8CVE-2024-0594: Awesome Support SQL Injection
CVE-2024-0594 - 8.1CVE-2023-5355: Awesome Support <= 6.1.4 Arbitrary File Deletion
CVE-2023-5355 - 7.5CVE-2025-58662: Awesome Support <= 6.3.5 PHP Object Injection
CVE-2025-58662 - 7.5CVE-2024-13567: Awesome Support Info Exposure
CVE-2024-13567 - 6.5CVE-2025-12641: Awesome Support Unauthenticated Role Demotion
CVE-2025-12641 - 6.5CVE-2015-9318: Awesome Support Arbitrary Shortcode Execution
CVE-2015-9318 - 5.4CVE-2023-49757: Awesome Support <= 6.1.10 Missing Authorization
CVE-2023-49757 - 5.3CVE-2026-4654: Awesome Support IDOR
CVE-2026-4654
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C