dbcve.org
Awesome SupportWordPress extension · Getawesomesupport

CVE-2023-48324

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 6.1.5 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.1.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Missing authorization vulnerability in the Awesome Support WordPress plugin (versions through 6.1.4) allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to sensitive support ticket data or administrative functions due to missing capability checks on certain plugin endpoints.

MitigationUpdate Awesome Support to the latest patched version and audit all plugin endpoints for proper authorization checks using WordPress capability functions (e.g., current_user_can()). If no patch is available, disable the plugin until a fix is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Awesome SupportWordPress extension
Affected:< 6.1.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Awesome Support plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or check if the /wp-content/plugins/awesome-support/ directory exists on the server
    Affected if The Awesome Support plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Awesome Support to view the version number, or read the main plugin file header for the Version field
    Affected if Version is listed as 6.1.4 or earlier (any version below 6.1.5)
  3. Inspect plugin endpoints for capability checks
    Examine the plugin PHP files in /wp-content/plugins/awesome-support/ for AJAX action handlers and admin page callbacks. Search for presence of current_user_can() or similar WordPress capability functions before executing sensitive operations on ticket data or administrative functions
    Affected if Sensitive endpoints lack proper current_user_can() or capability verification checks

The environment is affected if Awesome Support version is below 6.1.5 and the plugin endpoints handling support tickets or administrative functions are missing authorization capability checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.5 or later
Fixed in 6.1.5
Interim mitigation

Update Awesome Support to the latest patched version and audit all plugin endpoints for proper authorization checks using WordPress capability functions (e.g., current_user_can()). If no patch is available, disable the plugin until a fix is released.

Recommended fix High confidence

Awesome Support version 6.1.5

  1. Backup your WordPress database and files before making any changes
  2. Update the Awesome Support plugin to version 6.1.5 or later through the WordPress admin dashboard (Plugins > Installed Plugins > Awesome Support > Update Now)
  3. Alternatively, upload and replace the plugin files manually via FTP or hosting control panel
  4. After updating, verify the plugin status shows version 6.1.5 or higher in the Plugins list
  5. Test that key functionality (ticket creation, agent access, admin access) continues to work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Awesome Support Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-48324 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data