dbcve.org
Awesome SupportWordPress extension · Getawesomesupport

CVE-2024-35741

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 6.1.8 or later.
See remediation →
94/100
Remediation priority · Urgent
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.7.

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

A Missing Authorization vulnerability in the Awesome Support WordPress plugin (versions through 6.1.7) allows authenticated users to access functionality or perform actions that should be restricted to higher-privileged users. The lack of proper capability or permission checks enables attackers with standard user accounts to potentially escalate privileges or access administrative functions.

MitigationUpdate to the latest version of Awesome Support when available, or implement proper capability checks and authorization validation on all sensitive functions and AJAX actions within the plugin.

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

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
High
Integrity
High
Availability
High

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

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. Identify installed plugin version
    Check the Awesome Support plugin version in WordPress admin under Plugins > Installed Plugins, or inspect the main plugin file (e.g., awesome-support.php) and look for the 'Version:' header in the plugin comments
    Affected if The version listed is below 6.1.8 (e.g., 6.1.7, 6.1.6, etc.)
  2. Verify plugin is active
    Confirm the Awesome Support plugin is currently activated on the WordPress site by checking the Plugins admin page
    Affected if The plugin is active and the version is below 6.1.8
  3. Identify accessible AJAX actions
    Review the plugin directory (typically wp-content/plugins/awesome-support/) for PHP files containing 'add_action' hooks tied to 'wp_ajax_' actions. These are the endpoints the plugin exposes
    Affected if The plugin exposes AJAX action handlers without proper capability checks (requires code review or comparison to fixed version)
  4. Check registered user roles
    Inspect the WordPress user roles and capabilities via wp-admin > Users > Roles, or use a database query on wp_options for option_name containing 'user_roles'
    Affected if Standard authenticated users exist on the site and the vulnerable plugin version is installed

A site is affected if the Awesome Support plugin is installed and active at a version lower than 6.1.8, and the site has user accounts with standard privileges that could potentially access the unrestricted 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.8 or later
Fixed in 6.1.8
Interim mitigation

Update to the latest version of Awesome Support when available, or implement proper capability checks and authorization validation on all sensitive functions and AJAX actions within the plugin.

Recommended fix High confidence

Awesome Support version 6.1.8

  1. Create a complete backup of your WordPress site and database before making any changes
  2. Update the Awesome Support plugin to version 6.1.8 or later through the WordPress admin dashboard (Plugins > Add New > Upload or WP-Admin > Dashboard > Updates)
  3. Alternatively, update via FTP by uploading the new plugin files to wp-content/plugins/awesome-support/
  4. After updating, clear any caching mechanisms if used
  5. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  6. Test that ticket creation, assignment, and status changes work correctly to confirm authorization controls are functioning

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

Fix this in Awesome Support Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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