CVE-2024-54289
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 · uneditedMissing 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.3.1.
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 confidenceMissing Authorization vulnerability in Awesome Support WordPress plugin allows exploiting incorrectly configured access control security levels. The plugin fails to properly enforce authorization checks on certain functionality, potentially allowing unauthenticated or lower-privileged users to access sensitive features or perform actions beyond their intended permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Awesome Support plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Awesome Support', or check the plugin files in /wp-content/plugins/awesome-support/Affected if The plugin is installed and running
-
Determine installed plugin versionCheck the plugin version number in the plugin header (typically in main plugin file or in Plugins admin page), then compare to the affected range: version 6.3.1 and below are vulnerableAffected if Installed version is 6.3.1 or lower
-
Inspect access control configurationNavigate to WordPress admin > Awesome Support > Settings > Roles and Capabilities (or similar access control settings page). Review user role assignments and permission levels configured for the pluginAffected if Lower-privileged users (subscribers, customers, or non-logged-in users) are granted elevated permissions or access to admin-level features
-
Test for unauthorized feature accessIf you have a low-privileged test account (subscriber or customer role), attempt to access plugin admin functions or sensitive features that should require administrator-level accessAffected if Lower-privileged users can access features intended only for administrators
Your environment is affected if the Awesome Support plugin version is 6.3.1 or lower AND the access control settings allow unauthenticated or lower-privileged users to access sensitive administrative features.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade Awesome Support plugin to version > 6.3.1 to obtain the vendor patch. Review and configure access control settings to ensure proper security level enforcement.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-54289 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54289 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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