dbcve.org
Awesome SupportWordPress extension · Getawesomesupport

CVE-2023-49757

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 6.1.11 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.10.

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

The Awesome Support WordPress plugin has a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This means users can potentially access functionality or data they should not have permission to access due to improper or missing capability checks.

MitigationImplement proper authorization checks and capability verification on all sensitive functions and endpoints within the plugin, ensuring users can only access resources appropriate to their role.

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

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. Locate the installed Awesome Support plugin version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, find 'Awesome Support' or 'Getawesomesupport Awesome Support', and read the version number displayed below the plugin name. Alternatively, check the main plugin file (usually in wp-content/plugins/awesome-support/ or similar path) for the 'Version:' header comment.
    Affected if The displayed version number is lower than 6.1.11 (e.g., 6.1.10, 6.0.0, etc.) or if no version is displayed and the plugin has not been updated recently.
  2. Verify the plugin is active on the WordPress site
    In the WordPress admin under Plugins > Installed Plugins, confirm that Awesome Support shows as 'Active' rather than 'Inactive' or 'Must Use'.
    Affected if The plugin is active and the version is below 6.1.11.
  3. Review WordPress user roles with Awesome Support capabilities
    Using a role management plugin or via database query on wp_usermeta, examine which user roles (Administrator, Editor, Author, Contributor, Subscriber, or custom roles) have been assigned capabilities related to Awesome Support (typically 'awesome_support_' prefixed capabilities). Check for roles that may have elevated permissions without proper justification.
    Affected if Users in lower-privileged roles (such as Subscriber or Contributor) possess capabilities they should not have, or no capability verification is enforced on sensitive plugin functions.
  4. Inspect plugin access control settings
    Within the WordPress admin panel, locate the Awesome Support settings page (usually under Awesome Support > Settings or similar). Review any access control, permission, or role-based configuration options to determine if capability checks are properly enforced on sensitive endpoints or actions.
    Affected if The plugin settings allow unrestricted or improperly restricted access to administrative functions, or no capability verification is configured for ticket management, user management, or data export features.

Your environment is affected if the installed Awesome Support plugin version is below 6.1.11 and the plugin is active, as this version range contains the missing authorization vulnerability.

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

Implement proper authorization checks and capability verification on all sensitive functions and endpoints within the plugin, ensuring users can only access resources appropriate to their role.

Recommended fix High confidence

6.1.11

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Awesome Support' in the plugin list
  4. If an update is available, click 'Update Now' to update to version 6.1.11
  5. Alternatively, manually download version 6.1.11 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the version number in Plugins > Installed Plugins to confirm 6.1.11 is installed

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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