dbcve.org
Awesome SupportWordPress extension · Getawesomesupport

CVE-2024-24716

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 6.1.7 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 Awesome Support Team Awesome Support.This issue affects Awesome Support: from n/a through 6.1.6.

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 Awesome Support plugin allows authenticated users to access or modify resources they should not have permission to access. The issue likely involves missing capability checks or nonce validation on sensitive functions, enabling privilege escalation or unauthorized data access.

MitigationApply the vendor patch (version 6.1.7 or later) which adds proper authorization checks. Until patched, limit user access to only trusted, authorized personnel and monitor for suspicious activity.

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.7

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. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Awesome Support and read the version number. Alternatively, open the main plugin file (awesome-support.php) and look for the 'Version' header in the plugin comments.
    Affected if The installed version is lower than 6.1.7
  2. Verify plugin is active
    In WordPress admin, confirm Awesome Support is listed as an active (not deactivated) plugin.
    Affected if The plugin is active and version is below 6.1.7
  3. Identify user roles with access
    Go to Users > All Users in WordPress admin and review which users are assigned the Awesome Support agent or user roles provided by the plugin.
    Affected if There are users with Awesome Support roles (agent, manager, or user) other than trusted administrators, and the plugin version is vulnerable
  4. Review capability assignments
    Navigate to Awesome Support > Settings > Roles and Capabilities (or similar) to see which capabilities are assigned to non-administrator roles.
    Affected if Non-administrator roles have sensitive capabilities and the plugin version is below 6.1.7
  5. Audit admin actions for nonce validation
    Examine the plugin PHP files in wp-content/plugins/awesome-support/ for AJAX handlers or form processing functions that handle sensitive operations (tickets, user data, settings). Look for presence of 'current_user_can' capability checks and 'wp_verify_nonce' or 'check_admin_referer' calls.
    Affected if Sensitive functions lack capability checks or nonce verification and the plugin version is below 6.1.7

You are affected if Awesome Support plugin version is below 6.1.7 and non-administrator users have access to the plugin functionality.

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.7 or later
Fixed in 6.1.7
Interim mitigation

Apply the vendor patch (version 6.1.7 or later) which adds proper authorization checks. Until patched, limit user access to only trusted, authorized personnel and monitor for suspicious activity.

Recommended fix Moderate confidence

Awesome Support version 6.1.7

  1. 1. Create a full backup of your WordPress site before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find 'Awesome Support' in your installed plugins list
  4. 4. Click 'Update now' to update to the latest version (6.1.7 or later)
  5. 5. Alternatively, go to Plugins > Add New > Upload and upload the version 6.1.7 package from the WordPress repository
  6. 6. After update completes, verify the plugin is running version 6.1.7 or higher
  7. 7. Test that ticket creation, assignment, and user role functionality works correctly

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

Fix this in Awesome Support Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24716 — 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-2024-24716 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