An elevation of privilege vulnerability exists in Microsoft Dynamics 365 Commerce. An unauthenticated attacker who successfully exploited this vulnerability could update data without proper authorization.
To exploit the vulnerability, an attacker would need to send a specially crafted request to an affected server.
The security update addresses the vulnerability by correcting how Microsoft Dynamics 365 Commerce performs authorization checks.
## Which versions are affected by CVE-2020-16943? It affects 1 product. Products: Microsoft Dynamics 365. ## How do I fix CVE-2020-16943? No fix has been published for CVE-2020-16943 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-16943 being exploited? There is no known exploitation of CVE-2020-16943 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft Dynamics 365 - [CVE-2026-47647](https://insights.sbomify.com/CVE-2026-47647/): Dynamics 365 Elevation of Privilege Vulnerability (critical 9.9) - [CVE-2026-42898](https://insights.sbomify.com/CVE-2026-42898/): Microsoft Dynamics 365 On-Premises Remote Code Execution Vulnerability (critical 9.9) - [CVE-2026-32210](https://insights.sbomify.com/CVE-2026-32210/): Microsoft Dynamics 365 (online) Spoofing Vulnerability (critical 9.3) - [CVE-2026-42833](https://insights.sbomify.com/CVE-2026-42833/): Microsoft Dynamics 365 On-Premises Remote Code Execution Vulnerability (critical 9.1) - [CVE-2024-38182](https://insights.sbomify.com/CVE-2024-38182/): Microsoft Dynamics 365 Elevation of Privilege Vulnerability (critical 9.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-16943 and fix it if it is affected. What it is: CVE-2020-16943 is a medium-severity missing authorization vulnerability in Microsoft Dynamics 365, published on 16 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-16943 in the wild and no public exploit code. Affected product: Microsoft Dynamics 365. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-16943/ (Markdown: https://insights.sbomify.com/CVE-2020-16943/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-16943 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-16943 - OSV: https://osv.dev/vulnerability/CVE-2020-16943 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-16943/ Summaries are generated and may contain mistakes; the official description above is the record.