dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-28417

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 AlexaCRM Dynamics 365 Integration allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Dynamics 365 Integration: from n/a through 1.3.12.

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

Missing authorization vulnerability in AlexaCRM Dynamics 365 Integration allows attackers to exploit incorrectly configured access control security levels. The integration lacks proper authorization checks on certain functionality, enabling unauthenticated or lower-privileged users to access resources or perform actions they should not be permitted to access.

MitigationImplement proper authorization checks and enforce defined access control security levels across all integration endpoints and functions. Ensure role-based access control (RBAC) is correctly applied.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if AlexaCRM Dynamics 365 Integration is deployed
    Check your Dynamics 365 environment or connected systems for the presence of the AlexaCRM integration module/plugin. Look for any AlexaCRM-related components, add-ins, or connected applications in your system configuration.
    Affected if The integration is installed and running in your environment.
  2. Review access control security level configuration
    Locate and inspect the security settings for the AlexaCRM integration. Look for configuration options related to access control, security levels, or permission settings within the integration administration panel or configuration files.
    Affected if Security levels are set to allow unauthenticated access or are configured to permissive levels (e.g., 'None', 'Low', or 'Public').
  3. Verify authorization enforcement on integration endpoints
    Examine the integration's API endpoints, webhooks, or callback URLs. Check if these endpoints validate user authentication and authorization before executing actions or returning data.
    Affected if The integration endpoints do not require valid authentication tokens, session cookies, or API keys, or they accept requests from any user regardless of privilege level.
  4. Test for unauthorized resource access
    Attempt to access or query CRM resources (records, data, or administrative functions) through the integration using an account with no role, a basic user role, or no credentials at all. Observe whether the integration returns data or performs actions it should restrict.
    Affected if Unauthenticated requests or requests from low-privilege accounts can read, modify, or delete data or access administrative features that should require higher privileges.
  5. Confirm role-based access control is properly applied
    Check if the integration respects Dynamics 365 security roles and field-level security. Verify that API calls made through the integration honor the permission boundaries of the calling user's assigned security role.
    Affected if The integration bypasses Dynamics 365 security roles and allows access to resources outside the user's defined permission scope.

Your environment is affected if the AlexaCRM Dynamics 365 Integration is installed and lacks proper authorization enforcement, allowing unauthenticated or under-privileged access to resources or actions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks and enforce defined access control security levels across all integration endpoints and functions. Ensure role-based access control (RBAC) is correctly applied.

Recommended fix Moderate confidence

Plugin version 1.3.13 or later

  1. 1. Update the AlexaCRM Dynamics 365 Integration WordPress plugin to the latest available version
  2. 2. After updating, verify that the plugin functions correctly with your Dynamics 365 integration
  3. 3. Test that the authorization controls are working as expected

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

Have this fixed 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 help mitigating

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-2023-28417 — 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-28417 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