LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51537: WordPress Awesome Support plugin <= 6.1.5 - Broken Access Control vulnerability

Missing Authorization vulnerability in Awesome Support Team Awesome Support.This issue affects Awesome Support: from n/a through 6.1.5.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-51537 is a broken access control issue in the WordPress Awesome Support plugin through version 6.1.5. The scoring indicates a remote unauthenticated attacker could access some information without user interaction. Available sources do not state active exploitation or name a specific fixed version.

Executive priority

Treat this as a moderate WordPress exposure issue. Prioritize internet-facing sites that handle customer support data, because the CVSS vector indicates unauthorized information access, but not integrity or availability impact.

Technical view

The vulnerability is classified as CWE-862 Missing Authorization in Awesome Support Team's Awesome Support WordPress plugin, package name awesome-support. CVSS 3.1 is 5.3 with AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, indicating low-complexity network exploitation with limited confidentiality impact only.

Likely exposure

Exposure is most likely on public WordPress sites running Awesome Support version 6.1.5 or earlier. Sites not using this plugin, or using unaffected versions, are not indicated as exposed by the provided CVE data.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. Patchstack lists the issue as a vulnerability database entry, but the bundle does not include endpoint-level details, proof-of-concept status, or observed exploitation claims.

Researcher notes

Evidence is sufficient for affected product, affected range, CWE, and CVSS impact. Evidence is incomplete for root-cause location, affected endpoint, patch version, and exploit availability. Avoid assuming broader WordPress compromise from the provided data alone.

Mitigation direction

  • Inventory WordPress sites for the Awesome Support plugin and flag versions 6.1.5 or earlier.
  • Check Awesome Support or Patchstack guidance for a fixed version or vendor-recommended mitigation.
  • Update, disable, or remove the plugin where remediation guidance cannot be confirmed.
  • Review access logs for unusual unauthenticated requests to Awesome Support functionality.

Validation and detection

  • Confirm installed plugin version from WordPress administration or asset inventory.
  • Verify whether Awesome Support is active on internet-facing WordPress sites.
  • Check vendor or Patchstack records for remediation details before closing the finding.
  • Document whether any exposed site remains on version 6.1.5 or earlier.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-51537 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-51537Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Awesome Support TeamAwesome Supportawesome-support, n/aunaffected
Weakness

CWE details

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.