WordPress plugin · Updated daily · Source: Wordfence Intelligence

Awesome Support vulnerabilities: affected versions and fixes

Awesome Support has 6,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Awesome Support at a glance

  • 30 publicly disclosed vulnerabilities, 5 of them rated High or Critical. The most recent was disclosed on Oct 27, 2026.
  • Ranked #2885 by popularity on WordPress.org (6,000+ active installs).
  • The latest version is 6.4.2 (released Oct 16, 2026). The most recent security fix shipped in 6.4.2.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Awesome Support version

Enter the Awesome Support version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Awesome Support”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Awesome Support”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (6.4.2). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Awesome Support vulnerabilities (latest 25 of 30)

  • Awesome Support <= 6.4.1 - Authenticated (Custom+) Stored Cross-Site Scripting via Ticket Attachment MIME Confusion

    Cross-site scripting (XSS) · CVE-2026-103370

    Affected versions: ≤ 6.4.1

    Fixed in: 6.4.2

    Severity: Medium 6.4 · Disclosed Oct 27, 2026

  • Awesome Support <= 6.4.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'gdpr-data' Parameter via wpas_gdpr_user_opt_out AJAX Action

    Cross-site scripting (XSS) · CVE-2026-96268

    Affected versions: ≤ 6.4.0

    Fixed in: 6.4.1

    Severity: Medium 6.4 · Disclosed Sep 30, 2026

  • Awesome Support – WordPress HelpDesk & Support Plugin <= 6.3.9 - Authenticated (Subscriber+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-96820

    Affected versions: ≤ 6.3.9

    Fixed in: 6.4.0

    Severity: Medium 6.4 · Disclosed Sep 28, 2026

  • Awesome Support <= 6.3.9 - Missing Authorization to Authenticated (Subscriber+) Arbitrary User Denial via 'user_id' Parameter

    Missing authorization · CVE-2026-19946

    Affected versions: ≤ 6.3.9

    Fixed in: 6.4.0

    Severity: Medium 4.3 · Disclosed Sep 8, 2026

  • Awesome Support <= 6.3.7 - Authenticated (Subscriber+) Insecure Direct Object Reference to Unauthorized Ticket Reply Access via 'ticket_id' Parameter

    Missing authorization · CVE-2026-4654

    Affected versions: ≤ 6.3.7

    Fixed in: 6.3.8

    Severity: Medium 5.3 · Disclosed Apr 7, 2026

  • Awesome Support – WordPress HelpDesk & Support Plugin <= 6.3.6 - Missing Authorization to Unauthenticated Role Demotion

    Missing authorization · CVE-2025-12641

    Affected versions: ≤ 6.3.6

    Fixed in: 6.3.7

    Severity: Medium 6.5 · Disclosed Jan 15, 2026

  • Awesome Support <= 6.3.5 - Authenticated (Support Manager+) PHP Object Injection

    PHP object injection · CVE-2025-58662

    Affected versions: ≤ 6.3.5

    Fixed in: 6.3.6

    Severity: High 7.5 · Disclosed Sep 22, 2025

  • Awesome Support <= 6.3.6 - Information Exposure

    Information disclosure · CVE-2025-53340

    Affected versions: ≤ 6.3.6

    Fixed in: 6.3.7

    Severity: Medium 5.3 · Disclosed Aug 14, 2025

  • Awesome Support – WordPress HelpDesk & Support Plugin <= 6.3.1 - Unauthenticated Sensitive Information Exposure Through Unprotected Directory

    Information disclosure · CVE-2024-13567

    Affected versions: ≤ 6.3.1

    Fixed in: 6.3.2

    Severity: High 7.5 · Disclosed Mar 31, 2025

  • Awesome Support <= 6.3.1 - Missing Authorization

    Missing authorization · CVE-2024-54289

    Affected versions: ≤ 6.3.1

    Fixed in: 6.3.2

    Severity: Medium 4.3 · Disclosed Dec 11, 2024

  • Awesome Support <= 6.1.6 - Insufficient Authorization via wpas_can_delete_attachments()

    Other weakness · CVE-2024-24716

    Affected versions: ≤ 6.1.6

    Fixed in: 6.1.7

    Severity: Medium 4.3 · Disclosed Mar 12, 2024

  • Awesome Support – WordPress HelpDesk & Support Plugin <= 6.1.7 - Authenticated (Subscriber+) SQL Injection

    SQL injection · CVE-2024-0594

    Affected versions: ≤ 6.1.7

    Fixed in: 6.1.8

    Severity: High 8.8 · Disclosed Feb 9, 2024

  • Awesome Support – WordPress HelpDesk & Support Plugin <= 6.1.7 - Missing Authorization via editor_html()

    Missing authorization · CVE-2024-0596

    Affected versions: ≤ 6.1.7

    Fixed in: 6.1.8

    Severity: Medium 5.3 · Disclosed Feb 9, 2024

  • Awesome Support – WordPress HelpDesk & Support Plugin <= 6.1.7 - Missing Authorization via wpas_get_users()

    Missing authorization · CVE-2024-0595

    Affected versions: ≤ 6.1.7

    Fixed in: 6.1.8

    Severity: Medium 4.3 · Disclosed Feb 9, 2024

  • Awesome Support <= 6.1.5 - Missing Authorization via wpas_load_reply_history

    Missing authorization · CVE-2023-51537

    Affected versions: ≤ 6.1.5

    Fixed in: 6.1.6

    Severity: Medium 5.3 · Disclosed Dec 27, 2023

  • Awesome Support <= 6.1.5 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2023-51538

    Affected versions: ≤ 6.1.5

    Fixed in: 6.1.6

    Severity: Medium 4.3 · Disclosed Dec 27, 2023

  • Awesome Support <= 6.1.7 - Missing Authorization

    Missing authorization · CVE-2023-49857

    Affected versions: ≤ 6.1.7

    Fixed in: 6.1.8

    Severity: Medium 5.3 · Disclosed Dec 7, 2023

  • Awesome Support <= 6.1.10 - Missing Authorization

    Missing authorization · CVE-2023-49757

    Affected versions: ≤ 6.1.10

    Fixed in: 6.1.11

    Severity: Medium 5.4 · Disclosed Dec 4, 2023

  • Awesome Support <= 6.1.4 - Missing Authorization via wpas_edit_reply_ajax()

    Missing authorization · CVE-2023-48324

    Affected versions: ≤ 6.1.4

    Fixed in: 6.1.5

    Severity: Medium 4.3 · Disclosed Nov 23, 2023

  • Awesome Support <= 6.1.4 - Cross-Site Request Forgery via wpas_edit_reply_ajax()

    Cross-site request forgery (CSRF) · CVE-2023-48323

    Affected versions: ≤ 6.1.4

    Fixed in: 6.1.5

    Severity: Medium 4.3 · Disclosed Nov 23, 2023

  • Awesome Support <= 6.1.4 - Authenticated (Submitter+) Arbitrary File Deletion

    Arbitrary file read or deletion · CVE-2023-5355

    Affected versions: ≤ 6.1.4

    Fixed in: 6.1.5

    Severity: High 8.1 · Disclosed Oct 16, 2023

  • Awesome Support <= 6.1.4 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-5354

    Affected versions: ≤ 6.1.4

    Fixed in: 6.1.5

    Severity: Medium 6.1 · Disclosed Oct 16, 2023

  • Awesome Support <= 6.1.4 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Modification

    Missing authorization · CVE-2023-5352

    Affected versions: ≤ 6.1.4

    Fixed in: 6.1.5

    Severity: Medium 4.3 · Disclosed Oct 16, 2023

  • Awesome Support <= 6.1.1 - Insecure Direct Object Reference to (Subscriber+) Ticket Export

    Missing authorization · CVE-2022-3511

    Affected versions: ≤ 6.1.1

    Fixed in: 6.1.2

    Severity: Medium 4.3 · Disclosed Nov 7, 2022

  • Awesome Support <= 6.0.7 - Authenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-38073

    Affected versions: ≤ 6.0.7

    Fixed in: 6.0.8

    Severity: High 7.2 · Disclosed Sep 14, 2022

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 27, 2026.

Most common weaknesses in Awesome Support

Missing authorization

12 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Cross-site scripting (XSS)

9 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Information disclosure

2 issues

Data that should stay private, such as user details or configuration values, can be read from outside.

Frequently asked questions

Is Awesome Support safe to use?

Awesome Support is a well-known plugin with 6,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (6.4.2) and turn on automatic updates.

How do I find which version of Awesome Support my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesAwesome Support on WordPress.org