WordPress plugin
Browser-Update-Notify security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All Browser-Update-Notify vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Reflected Cross-Site Scripting ≤0.2.1No patch available | CVE-2025-23490 |
- Medium6.1Reflected Cross-Site Scripting
≤0.2.1No patch available
Browser-Update-Notify: common questions
Does Browser-Update-Notify have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Browser-Update-Notify: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Browser-Update-Notify I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Browser-Update-Notify vulnerability?
CVE-2025-23490, published Jan 16, 2025: Browser-Update-Notify <= 0.2.1 - Reflected Cross-Site Scripting. Severity: Medium (CVSS 6.1).
Is any Browser-Update-Notify vulnerability listed in CISA KEV?
No. None of the known Browser-Update-Notify vulnerabilities is currently listed in the CISA KEV catalog.