WordPress plugin
de:branding 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
- High2
- Medium0
- Low0
All de:branding vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.8 | Authenticated (Subscriber+) Arbitrary Options Update ≤1.0.2No patch available | CVE-2024-11443 | |
| High8.8 | Privilege Escalation ≤1.0.2No patch available | CVE-2024-52438 |
- High8.8Authenticated (Subscriber+) Arbitrary Options Update
≤1.0.2No patch available
- High8.8Privilege Escalation
≤1.0.2No patch available
de:branding: common questions
Does de:branding have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in de:branding: 2 high. At least one is not fixed in the latest version.
How do I check which version of de: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 de:branding vulnerability?
CVE-2024-11443, published Dec 11, 2024: de:branding <= 1.0.2 - Authenticated (Subscriber+) Arbitrary Options Update. Severity: High (CVSS 8.8).
Is any de:branding vulnerability listed in CISA KEV?
No. None of the known de:branding vulnerabilities is currently listed in the CISA KEV catalog.