Awesome SupportWordPress extension · Getawesomesupport
CVE-2022-38073
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple Authenticated (custom specific plugin role) Persistent Cross-Site Scripting (XSS) vulnerability in Awesome Support plugin <= 6.0.7 at WordPress.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAuthenticated persistent Cross-Site Scripting (XSS) vulnerability in Awesome Support WordPress plugin <= 6.0.7 affecting users with a specific custom plugin role. The flaw allows an attacker with the specific role to inject malicious JavaScript that gets stored in the database and executes when other users view the compromised content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Awesome SupportWordPress extension
<= 6.0.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Awesome Support plugin versionGo to WordPress Admin > Plugins > Installed Plugins, locate 'Awesome Support' or 'Getawesomesupport Awesome Support', and note the version number displayedAffected if Version is 6.0.7 or lower
-
Identify custom plugin roleNavigate to WordPress Admin > Users > Roles, or use a role management plugin or WP-CLI command 'wp role list' to enumerate all roles and look for a custom role associated with Awesome Support (may be named 'Agent', 'Support Agent', or a custom capability set)Affected if A custom role with elevated plugin-specific capabilities exists in the WordPress installation
-
Check for users assigned the custom roleIn WordPress Admin > Users, filter by the custom role identified in the previous step, or use WP-CLI: 'wp user list --role=[role_name]'Affected if One or more users are assigned the custom plugin-specific role
-
Audit stored content for potential XSS payloadsQuery the WordPress database (wp_posts, wp_postmeta tables) for ticket-related content containing suspicious patterns like <script>, javascript:, onload=, onerror=, or other HTML/JS tags. Use SQL: SELECT * FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%javascript:%'Affected if Stored content contains unrecognized or malicious script tags or event handlers
Environment is affected if Awesome Support plugin version is 6.0.7 or lower AND a custom plugin role exists with at least one assigned user who could have injected malicious scripts into ticket data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Awesome Support plugin to a version newer than 6.0.7. If immediate update is not possible, audit users assigned the custom plugin role and implement Content Security Policy (CSP) headers as a defensive measure.
Latest available version on wordpress.org (version > 6.0.7)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the Awesome Support plugin
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin is functioning correctly on the frontend and backend
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Awesome Support
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38073 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data