WordPress theme
Brilliance security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the theme or restrict access to the affected feature until the vendor ships a patch.
- Critical1
- High0
- Medium2
- Low0
All Brilliance vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Reflected Cross-Site Scripting ≤1.3.1No patch available | CVE-2023-28171 | |
| Critical9.8 | Function Injection ≤2.4.8Update to 2.4.9 | CVE-2020-36708 | |
| Medium6.5 | Unauthenticated Plugin Activation/Deactivation ≤1.3.1Update to 1.3.2 | CVE-2020-36721 |
- Medium6.1Reflected Cross-Site Scripting
≤1.3.1No patch available
- Critical9.8Function Injection
≤2.4.8Update to 2.4.9
- Medium6.5Unauthenticated Plugin Activation/Deactivation
≤1.3.1Update to 1.3.2
Brilliance: common questions
Does Brilliance have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in Brilliance: 1 critical, 2 medium. At least one is not fixed in the latest version.
How do I check which version of Brilliance I run?
In wp-admin open Appearance → Themes and select the theme; 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 Brilliance vulnerability?
CVE-2023-28171, published Mar 13, 2023: Brilliance <= 1.3.1 - Reflected Cross-Site Scripting. Severity: Medium (CVSS 6.1).
Is any Brilliance vulnerability listed in CISA KEV?
No. None of the known Brilliance vulnerabilities is currently listed in the CISA KEV catalog.