How severe is CVE-2022-3511?

CVE-2022-3511 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2022-3511 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-3511?

CVE-2022-3511 affects Getawesomesupport Awesome Support. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-3511?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2022-3511 published?

CVE-2022-3511 was published on 2022-11-28 and last updated on 2026-06-17.

CVE-2022-3511

CVE-2022-3511 is a medium-severity vulnerability in Getawesomesupport Awesome Support with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
EPSS exploit prediction: 1% (49th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Getawesomesupport Awesome Support
Published: 2022-11-28
Last modified: 2026-06-17

Description

The Awesome Support WordPress plugin before 6.1.2 does not ensure that the exported tickets archive to be downloaded belongs to the user making the request, allowing a low privileged user, such as subscriber to download arbitrary exported tickets via an IDOR vector

Frequently asked questions

What is CVE-2022-3511?: The Awesome Support WordPress plugin before 6.1.2 does not ensure that the exported tickets archive to be downloaded belongs to the user making the request, allowing a low privileged user, such as subscriber to download arbitrary exported tickets via an IDOR vector
How severe is CVE-2022-3511?: CVE-2022-3511 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2022-3511 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-3511?: CVE-2022-3511 affects Getawesomesupport Awesome Support. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-3511?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2022-3511 published?: CVE-2022-3511 was published on 2022-11-28 and last updated on 2026-06-17.

References

https://wpscan.com/vulnerability/9e57285a-0023-4711-874c-6e7b3c2673d1

Affected products (1)

cpe:2.3:a:getawesomesupport:awesome_support:*:*:*:*:*:wordpress:*:*

More vulnerabilities in Getawesomesupport Awesome Support

CVE-2024-0594 — High (CVSS 8.8): The Awesome Support – WordPress HelpDesk & Support Plugin plugin for WordPress is vulnerable to union-based SQL…
CVE-2023-5355 — High (CVSS 8.1): The Awesome Support WordPress plugin before 6.1.5 does not sanitize file paths when deleting temporary attachment…
CVE-2015-9318 — High (CVSS 7.5): The awesome-support plugin before 3.1.7 for WordPress has a security issue in which shortcodes are allowed in replies.
CVE-2023-49857 — Medium (CVSS 6.5): Missing Authorization vulnerability in awesomesupport Awesome Support awesome-support allows Exploiting Incorrectly…
CVE-2023-5354 — Medium (CVSS 6.1): The Awesome Support WordPress plugin before 6.1.5 does not sanitise and escape a parameter before outputting it back in…
CVE-2021-36919 — Medium (CVSS 6.1): Multiple Authenticated Reflected Cross-Site Scripting (XSS) vulnerabilities in WordPress Awesome Support plugin…

All CVEs affecting Getawesomesupport Awesome Support →