CVE-2022-41127: Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central (On Premises) Remote Code Execution Vulnerability
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 77.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Dec 13, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.7% · 77th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 8.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | dynamics 365 business central | cpe:2.3:a:microsoft:dynamics_365_business_central |
| microsoft | dynamics nav | cpe:2.3:a:microsoft:dynamics_nav |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft dynamics 365 business central2019
- microsoft dynamics 365 business central2020
- microsoft dynamics 365 business central2021
- microsoft dynamics 365 business central2022
- microsoft dynamics nav2016
- microsoft dynamics nav2017
- microsoft dynamics nav2018
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Dynamics 365 Business Central 2019 Release Wave 2 (On-Premise)
- 15.0.0 and later · before App Build 15.17.48428, Platform Build 15.0.48affected
Microsoft Dynamics 365 Business Central Spring 2019 Update
- 14.0.0 and later · before App Build 14.43.49498, Platform Build 14.0.49494affected
Microsoft Microsoft Dynamics 365 Business Central 2020 Release Wave 1
- 16.0.0 and later · before App Build 16.19.35126, Platform Build 16.35120affected
Microsoft Microsoft Dynamics 365 Business Central 2020 Release Wave 2
- 17.0.0 and later · before App Build 17.17.38111, Platform Build 17.0.38061affected
Microsoft Microsoft Dynamics 365 Business Central 2021 Release Wave 1
- 18.0.0 and later · before App Build 18.18.46920, Platform Build 18.0.46905affected
Microsoft Microsoft Dynamics 365 Business Central 2021 Release Wave 2
- 19.0.0 and later · before App Build 19.14.49970, Platform Build 19.0.49925affected
Microsoft Microsoft Dynamics 365 Business Central 2022 Release Wave 1
- 20.0.0 and later · before App Build 20.8.49971, Platform Build 20.0.49947affected
Microsoft Microsoft Dynamics 365 Business Central 2022 Release Wave 2
- 21.0.0 and later · before App Build 21.2.49990, Platform Build 21.0.49984affected
Microsoft Microsoft Dynamics NAV 2013 R2
- 1.0 and later · before 52297affected
Microsoft Microsoft Dynamics NAV 2015
- 1.0 and later · before 52204affected
Microsoft Microsoft Dynamics NAV 2016
- 1.0 and later · before Build 52203affected
Microsoft Microsoft Dynamics NAV 2017
- 1.0 and later · before Build 30712affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-38225Microsoft Dynamics 365 Business Central Elevation of Privilege Vulnerability39Monitor
- CVE-2024-35249Microsoft Dynamics 365 Business Central Remote Code Execution Vulnerability36Monitor
- CVE-2024-43460Dynamics 365 Business Central Elevation of Privilege Vulnerability35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-36946Aug 12, 2021 · Microsoft Dynamics Business Central Cross-site Scripting Vulnerability21Monitor
- ← EarlierCVE-2021-40440Sep 15, 2021 · Microsoft Dynamics Business Central Cross-site Scripting Vulnerability21Monitor
- Later →CVE-2023-38167Aug 8, 2023 · Microsoft Dynamics 365 Business Central Elevation of Privilege Vulnerability28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.