VulnerabilityPublished 29 Oct 2026

CVE-2026-48202: Brave (WordPress plugin) · Basic XSS

Affects Brave (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.8.9 when convenient.

Data as of 29 Oct 2026, 14:52 UTC

CVSS 3.1 base score

5.3Medium

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (Patchstack)	CVSS 3.1	5.3

Patch: Available – fixed in 0.8.9

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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

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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Upgrade Brave (WordPress plugin) to 0.8.9.

Affected software

Product	Affected	Fixed in
Bravebrave-popup-builder	Affected <0.8.9	Fixed in 0.8.9

AI-suggested

A fix for this vulnerability is available in Brave version 0.8.9. Users and administrators should update to version 0.8.9 or later to remediate this issue.

Description

CVE-2026-48202 is a medium severity vulnerability in the Brave browser affecting versions before 0.8.9. It involves improper neutralization of script-related HTML tags in a web page, leading to a basic cross-site scripting (XSS) issue in the brave-popup-builder component. This vulnerability allows code injection but does not impact confidentiality, integrity, or availability beyond limited information disclosure.

Impact

The vulnerability allows an attacker to inject script code into web pages, potentially leading to limited information disclosure. According to the CVSS vector, the impact on confidentiality is low, with no impact on integrity or availability. There is no indication of privilege requirements or user interaction needed for exploitation.

Summary

This vulnerability (CVE-2026-48202) in Brave browser versions prior to 0.8.9 is caused by improper neutralization of script-related HTML tags in the brave-popup-builder, enabling basic cross-site scripting (XSS) attacks. The flaw allows an attacker to inject code into web pages rendered by the browser. The issue is fixed in Brave version 0.8.9.

References

patchstack.com/database/wordpress/plugin/brave-popup-builder/vulnerability/wordpress-brave-plugin-0-8-8-content-injection-vulnerability?_s_id=cve (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 14:20 UTC

Technical details

References

Community reviews

Related threats