CVE-2023-36727VulnerabilityPublished 15 Sep 2023Updated 30 Oct 2025

CVE-2023-36727: Microsoft Edge (Chromium-based) · Spoofing

Affects Microsoft Edge (Chromium-based)Source CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:U/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Sep 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Microsoft Microsoft Edge (Chromium-based)	Affected =1.0.0	Fixed in–

AI-suggested

Organizations should prioritize updating Microsoft Edge to the latest patched version as soon as it becomes available from Microsoft. Until patches are applied, implementing strict Content Security Policies (CSP) can help reduce the risk of malicious content injection and limit the impact of spoofing attempts. User education campaigns focused on recognizing phishing and spoofing attempts are critical, emphasizing caution when interacting with unexpected links or prompts in the browser. Deploying endpoint protection solutions that monitor browser behavior and block suspicious activities can provide additional defense layers. Network-level protections such as web filtering and DNS security can help prevent access to known malicious sites exploiting this vulnerability. Administrators should audit browser extensions and remove any that are unnecessary or untrusted, as they can increase attack vectors. Monitoring for unusual authentication attempts or data exfiltration patterns can help detect exploitation attempts early. Finally, organizations should maintain an incident response plan that includes scenarios involving browser-based spoofing attacks.

Description

Microsoft Edge (Chromium-based) Spoofing Vulnerability

Impact

For European organizations, this vulnerability poses risks primarily to confidentiality and integrity of sensitive information accessed via Microsoft Edge. Attackers could use spoofed content to trick employees into divulging credentials, financial data, or proprietary information, potentially leading to data breaches or unauthorized access to corporate resources. The medium severity and requirement for user interaction mean that phishing and social engineering remain the primary exploitation vectors. Sectors such as finance, healthcare, government, and critical infrastructure, which depend heavily on secure web communications, could face targeted attacks leveraging this flaw. The impact could extend to reputational damage, regulatory penalties under GDPR if personal data is compromised, and operational disruptions if attackers gain footholds through credential theft. Since availability is not affected, direct service outages are unlikely, but the indirect consequences of compromised user trust and data leakage are significant. Organizations with large deployments of Microsoft Edge, especially those slow to apply updates, are at heightened risk. The vulnerability's scope change also suggests potential cross-process impacts, increasing the attack surface within the browser environment.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2025, 19:16 UTC

Technical details

References

Community reviews

Related threats