CVE-2024-54289: WordPress Awesome Support plugin <= 6.3.1 - Broken Access Control vulnerability
Missing Authorization vulnerability in awesomesupport Awesome Support awesome-support allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Awesome Support: from n/a through <= 6.3.1.
Security readout for executives and security teams
Plain-English summary
CVE-2024-54289 is a broken access control issue in the WordPress Awesome Support plugin. An authenticated user may be able to access information they should not see. The main business concern is confidentiality, not service outage or data tampering, based on the provided CVSS vector.
Executive priority
Prioritize within normal vulnerability remediation cycles, faster for customer-support portals containing sensitive tickets or regulated data. The issue is moderate severity, authenticated, and confidentiality-focused, with no supplied evidence of active exploitation.
Technical view
The issue is CWE-862 Missing Authorization in Awesome Support, affecting versions through 6.3.1 per the CVE description. CVSS 3.1 is 6.5: network reachable, low complexity, privileges required, no user interaction, high confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running the Awesome Support plugin at affected versions and allowing authenticated user access. The CVSS vector requires privileges, so anonymous internet-wide exploitation is not supported by the supplied evidence.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Treat this as a plausible authenticated access-control risk until vendor or Patchstack guidance confirms fixed versions and practical impact.
Researcher notes
Evidence is sparse. The CVE bundle names versions through 6.3.1, while the Patchstack URL slug references 6.3.0; verify the live advisory before final scoping. Do not assume a fixed version unless vendor guidance states one.
Mitigation direction
Inventory WordPress sites using the Awesome Support plugin.
Check vendor or Patchstack guidance for the fixed version.
Upgrade affected plugin installations when a vendor-supported fix is available.
Disable the plugin if exposure cannot be accepted before upgrade.
Review user roles with access to support functionality.
Validation and detection
Confirm whether Awesome Support is installed and enabled.
Record the installed plugin version on each WordPress site.
Compare versions against the CVE affected range through 6.3.1.
Review logs for unusual authenticated access to support data.
Validate remediation after upgrade or plugin removal.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.