Awesome SupportWordPress extension · Getawesomesupport
CVE-2023-49857
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.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 confidenceMissing Authorization vulnerability in the Awesome Support WordPress plugin allows authenticated users to exploit incorrectly configured access control security levels. This is likely an Insecure Direct Object Reference (IDOR) or broken access control issue where certain functions or data endpoints lack proper capability checks, allowing lower-privileged users to access or modify data they should not be able to.
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
< 6.1.8CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin versionNavigate to WordPress admin dashboard > Plugins > Awesome Support and check the installed version number, or inspect the main plugin file (e.g., awesome-support.php) for the version defineAffected if Installed version is lower than 6.1.8
-
Identify registered AJAX handlersSearch the plugin directory for add_action('wp_ajax_...) calls and review each handler for capability verification using current_user_can() or similar authorization functionsAffected if Any AJAX handlers lack proper capability checks before processing user requests
-
Review REST API endpointsInspect plugin files for register_rest_route() calls and verify each endpoint includes permission_callback functions that validate user roles or capabilitiesAffected if REST endpoints exist without permission_callback or with weak permission validation
-
Check custom capability configurationsLook for custom role definitions or capability modifications in the plugin settings (Settings > Awesome Support > Capabilities) and verify which user roles can access sensitive functionsAffected if Lower-privileged user roles (e.g., subscriber) have access to admin or agent-level functions
-
Inspect data retrieval functionsReview functions that fetch, update, or delete ticket data (typically in includes/ or templates/ directories) for direct object references without ownership verificationAffected if Ticket data can be accessed or modified by users who do not own the ticket
A user is affected if the installed Awesome Support plugin version is below 6.1.8 and any AJAX handlers, REST endpoints, or data functions lack proper capability checks allowing unauthorized access to ticket data.
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.
dbcve · scoped6.1.8
Update to a patched version of Awesome Support if available. If no patch exists, audit all AJAX handlers and data retrieval functions for proper authorization checks using current_user_can() or role-based capability validation.
6.1.8
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find "Awesome Support" in the plugin list
- Check if an update to version 6.1.8 is available
- If update available, click "Update Now" to upgrade to version 6.1.8
- If no automatic update appears, manually download version 6.1.8 from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
- After updating, verify the new version is active and functioning 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
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 locallyCheck whether your project pulls in CVE-2023-49857 — 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-2023-49857 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