Security readout for executives and security teams
Plain-English summary
Awesome Support for WordPress exposed user data, including email addresses, to any logged-in user with subscriber-level access or higher. The issue is not described as full site takeover, but it can leak information that supports phishing, account targeting, or privacy incidents.
Executive priority
Treat this as a moderate privacy and account-targeting risk. Prioritize internet-facing WordPress sites with customer portals, open registration, or sensitive user lists before lower-exposure internal sites.
Technical view
CVE-2024-0595 is a CWE-862 missing authorization issue in the AJAX-exposed wpas_get_users() function in Awesome Support up to and including 6.1.7. CVSS 3.1 is 4.3: network-reachable, low complexity, low privileges required, no user interaction, low confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running Awesome Support versions up to 6.1.7 where untrusted or broadly available user registration creates subscriber-level accounts.
Exploitation context
The provided sources do not cite active exploitation, and the CVE is not listed as KEV. Abuse requires an authenticated WordPress account, but subscriber access may be easy to obtain on sites with open registration.
Researcher notes
The issue centers on authorization, not authentication bypass. CVE-2024-35741 is noted as likely duplicate. Sources identify user data disclosure such as emails; they do not provide evidence of broader data access or exploitation in the wild.
Mitigation direction
- Inventory WordPress sites using Awesome Support and identify versions up to 6.1.7.
- Update Awesome Support beyond 6.1.7 after confirming vendor or WordPress plugin guidance.
- Disable open user registration where it is not operationally required.
- Review subscriber-level accounts and remove unnecessary or suspicious users.
- Monitor vendor and Wordfence advisories for confirmed fix details.
Validation and detection
- Confirm the installed Awesome Support version on each WordPress site.
- Review plugin code or release notes for capability checks around wpas_get_users().
- Check whether anonymous or subscriber registration is enabled on affected sites.
- Review logs for unusual authenticated AJAX activity involving user lookup behavior.
- Validate in staging that low-privilege users cannot access user data.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-0595 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/bfb77432-e58d-466e-a366-8b8d7f1b6982?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/awesome-support/trunk/includes/functions-user.php#L765CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3033134%40awesome-support&new=3033134%40awesome-support&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.