What is the severity of CVE-2018-8607?

CVE-2018-8607 is rated as a critical security vulnerability due to its potential for cross-site scripting attacks.

How do I fix CVE-2018-8607?

To fix CVE-2018-8607, update Microsoft Dynamics 365 (on-premises) to the latest patched version as recommended by Microsoft.

What software is affected by CVE-2018-8607?

CVE-2018-8607 affects Microsoft Dynamics 365 (on-premises) version 8, specifically versions between 8.0 and 8.2.3.0003.

What are the consequences of CVE-2018-8607?

Exploitation of CVE-2018-8607 can allow attackers to execute arbitrary scripts in the context of a user's session in Dynamics 365.

Is there a workaround for CVE-2018-8607?

Currently, there are no official workarounds for CVE-2018-8607, so upgrading to a secure version is essential.

Vulnerability/
CVE-2018-8607

medium

5.4

CWE

14/11/2018

5/8/2024

CVE-2018-8607: XSS

First published: Wed Nov 14 2018(Updated: )

A cross site scripting vulnerability exists when Microsoft Dynamics 365 (on-premises) version 8 does not properly sanitize a specially crafted web request to an affected Dynamics server, aka "Microsoft Dynamics 365 (on-premises) version 8 Cross Site Scripting Vulnerability." This affects Microsoft Dynamics 365. This CVE ID is unique from CVE-2018-8605, CVE-2018-8606, CVE-2018-8608.

Credit: secure@microsoft.com

Affected Software	Affected Version	How to fix
Microsoft Dynamics 365	>=8.0<8.2.3.0003

Remedy

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8607

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-8607?
CVE-2018-8607 is rated as a critical security vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2018-8607?
To fix CVE-2018-8607, update Microsoft Dynamics 365 (on-premises) to the latest patched version as recommended by Microsoft.
What software is affected by CVE-2018-8607?
CVE-2018-8607 affects Microsoft Dynamics 365 (on-premises) version 8, specifically versions between 8.0 and 8.2.3.0003.
What are the consequences of CVE-2018-8607?
Exploitation of CVE-2018-8607 can allow attackers to execute arbitrary scripts in the context of a user's session in Dynamics 365.
Is there a workaround for CVE-2018-8607?
Currently, there are no official workarounds for CVE-2018-8607, so upgrading to a secure version is essential.

collector/nvd-index
agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/weakness
agent/last-modified-date
agent/author
agent/remedy
agent/severity
agent/softwarecombine
agent/description
agent/first-publish-date
agent/event
agent/tags
agent/source
vendor/microsoft
canonical/microsoft dynamics 365
version/microsoft dynamics 365/8.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-8607?
CVE-2018-8607 is rated as a critical security vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2018-8607?
To fix CVE-2018-8607, update Microsoft Dynamics 365 (on-premises) to the latest patched version as recommended by Microsoft.
What software is affected by CVE-2018-8607?
CVE-2018-8607 affects Microsoft Dynamics 365 (on-premises) version 8, specifically versions between 8.0 and 8.2.3.0003.
What are the consequences of CVE-2018-8607?
Exploitation of CVE-2018-8607 can allow attackers to execute arbitrary scripts in the context of a user's session in Dynamics 365.
Is there a workaround for CVE-2018-8607?
Currently, there are no official workarounds for CVE-2018-8607, so upgrading to a secure version is essential.