CVE-2025-66099
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 ThemeAtelier Chat Help chat-help allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Chat Help: from n/a through <= 3.1.3.
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 confidenceThis is a Missing Authorization vulnerability in the ThemeAtelier Chat Help WordPress plugin (chat-help). The plugin fails to properly enforce access control checks on certain functionality, allowing users to exploit incorrectly configured security levels. This could permit unauthenticated or lower-privileged users to access administrative features or perform actions that should require higher privileges.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify if the Chat Help plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'chat-help' or search for files containing 'chat-help' in the plugin directoryAffected if The chat-help plugin folder exists in the WordPress plugins directory
-
Determine the installed plugin versionCheck the plugin's main PHP file (usually chat-help.php) for the 'Version' header in the plugin comment block, or check the plugin's readme.txt fileAffected if The installed version matches or falls within any vulnerable version range for this plugin
-
Identify AJAX endpoints exposed by the pluginExamine the plugin's PHP files for wp_ajax_ and wp_ajax_nopriv_ action hooks. Look for functions registered without proper capability checks using current_user_can()Affected if AJAX endpoints are registered without capability checks or without checking user authentication status
-
Test for unauthenticated access to admin functionsSubmit requests to identified AJAX endpoints without providing authentication credentials (not logged in) to see if actions execute successfullyAffected if The plugin allows unauthenticated or low-privilege users to execute administrative actions that should require higher privileges
-
Review plugin capability requirementsInspect the plugin source code for current_user_can() calls and WordPress capability checks (e.g., manage_options, edit_posts) on sensitive functions and AJAX handlersAffected if Sensitive functions lack capability checks or use weak/incorrect capability requirements
A user is affected if the Chat Help plugin is installed and its AJAX endpoints or administrative functions lack proper authorization checks, allowing unauthenticated or low-privilege users to access features that should require higher WordPress capabilities.
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 dataImplement proper authorization checks (capability checks and nonce verification) on all sensitive functions and AJAX endpoints within the plugin. Restrict access to administrative features to users with appropriate WordPress capabilities (e.g., manage_options).
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66099 — 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-2025-66099 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