WordPress plugin
Debrandify · Remove or Replace WordPress Branding security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 1 known vulnerability is fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High0
- Medium1
- Low0
All Debrandify · Remove or Replace WordPress Branding vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.4 | Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload ≤1.1.2Update to 1.1.3 | CVE-2024-9674 |
- Medium6.4Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload
≤1.1.2Update to 1.1.3
Debrandify · Remove or Replace WordPress Branding: common questions
Does Debrandify · Remove or Replace WordPress Branding have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Debrandify · Remove or Replace WordPress Branding: 1 medium. None are known to affect version null.
How do I check which version of Debrandify · Remove or Replace WordPress Branding 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 Debrandify · Remove or Replace WordPress Branding vulnerability?
CVE-2024-9674, published Oct 17, 2024: Debrandify · Remove or Replace WordPress Branding <= 1.1.2 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload. Severity: Medium (CVSS 6.4).
Is any Debrandify · Remove or Replace WordPress Branding vulnerability listed in CISA KEV?
No. None of the known Debrandify · Remove or Replace WordPress Branding vulnerabilities is currently listed in the CISA KEV catalog.