Security readout for executives and security teams
Plain-English summary
CVE-2023-51538 is a CSRF issue in the Awesome Support WordPress helpdesk plugin through version 6.1.5. A victim must interact with attacker-controlled content, and the documented impact is limited integrity loss. Treat it as a moderate WordPress hygiene issue, especially on sites where support workflows affect customers or operations.
Executive priority
Handle in the next routine WordPress patch cycle unless the plugin supports sensitive customer workflows or administrative actions. There is no supplied evidence of active exploitation, but exposed helpdesk sites should not remain on affected versions indefinitely.
Technical view
The CVE describes CWE-352 Cross-Site Request Forgery in package awesome-support, affecting Awesome Support – WordPress HelpDesk & Support Plugin through 6.1.5. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges required, user interaction required, low integrity impact, no confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress installations running Awesome Support through 6.1.5. The source bundle does not identify the vulnerable action, required victim role, or whether default configurations are exposed.
Exploitation context
CISA KEV is false, and the supplied sources do not state active exploitation. Abuse requires user interaction, consistent with CSRF. No exploit details, public weaponization, or proof-of-concept status are provided in the source bundle.
Researcher notes
The public bundle is sparse. It confirms CSRF, affected plugin family, version boundary through 6.1.5, CWE-352, and CVSS vector. It does not name the vulnerable endpoint, nonce failure, affected role, exploitability details, fixed version, or mitigation status.
Mitigation direction
- Inventory WordPress sites for the awesome-support plugin and installed version.
- Prioritize remediation for versions through 6.1.5.
- Check Awesome Support and Patchstack guidance for fixed versions or official mitigations.
- If no vendor fix is available, assess disabling the plugin on high-risk sites.
- Limit administrative access and review support workflow permissions.
Validation and detection
- Confirm whether each WordPress site runs Awesome Support version 6.1.5 or earlier.
- Check plugin inventory against the package name awesome-support.
- Review vendor and Patchstack advisories for current remediation status.
- Inspect audit logs for unexpected Awesome Support configuration or ticket changes.
- Document any sites where plugin version or usage cannot be confirmed.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2023-51538 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:N/UI:R/S:U/C:N/I:L/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:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.