LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48323: WordPress Awesome Support Plugin <= 6.1.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Awesome Support Team Awesome Support – WordPress HelpDesk & Support Plugin allows Cross Site Request Forgery.This issue affects Awesome Support – WordPress HelpDesk & Support Plugin: from n/a through 6.1.4.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-48323 is a CSRF flaw in the WordPress Awesome Support helpdesk plugin through version 6.1.4. It could let an attacker cause a logged-in user to perform an unintended action. The known impact is limited integrity compromise, not data theft or service outage.

Executive priority

Treat this as a moderate-priority WordPress plugin issue. It is not currently evidenced as exploited in the provided sources, but exposed helpdesk sites should be checked and remediated through vendor guidance because the flaw can affect site integrity.

Technical view

The CVE record identifies CWE-352 Cross-Site Request Forgery in Awesome Support Team's Awesome Support WordPress plugin, package `awesome-support`, affecting versions through 6.1.4. CVSS 3.1 is 4.3: network reachable, low attack complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact only.

Likely exposure

Exposure is likely limited to WordPress sites with the Awesome Support plugin installed and active at version 6.1.4 or earlier. Sites without this plugin, or on unaffected versions, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. The CVSS vector requires user interaction, consistent with CSRF, so practical abuse depends on tricking an authenticated user into taking attacker-influenced action.

Researcher notes

Evidence is sparse: the bundle provides CVE metadata, CVSS, CWE-352, affected plugin range through 6.1.4, and a Patchstack entry. It does not provide exploit details, vulnerable endpoints, proof of active exploitation, or a named fixed release.

Mitigation direction

  • Inventory WordPress sites for the `awesome-support` plugin.
  • Check whether installed versions are 6.1.4 or earlier.
  • Review Awesome Support or Patchstack guidance for fixed-version details.
  • Update, disable, or remove the plugin according to vendor guidance.
  • Prioritize sites where privileged users routinely access WordPress admin.

Validation and detection

  • Confirm the plugin is installed and active on each WordPress site.
  • Record the exact Awesome Support plugin version.
  • Verify whether the version is 6.1.4 or earlier.
  • Check vendor or Patchstack advisories for remediation status.
  • Review access logs for unusual administrative changes, if exposed.
Prepared
Confidence
high
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-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 lookup
cve · low confidence lookup

CVE-2023-48323 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
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

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 Support – WordPress HelpDesk & Support Pluginawesome-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-352 · source CWE mapping

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.