WordPress theme
Sakala 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.
- Critical0
- High3
- Medium0
- Low0
All Sakala vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.8 | Cross-Site Request Forgery ≤1.4.2Update to 1.4.3 | — | |
| High8.8 | Missing Authorization to Arbitrary Plugin Deactivation/Activation ≤1.4.2Update to 1.4.3 | CVE-2022-23975 | |
| High8.8 | Authenticated (Subscriber+) Arbitrary File Upload ≤1.4.2Update to 1.4.3 | CVE-2021-39317 |
- High8.8Cross-Site Request Forgery
≤1.4.2Update to 1.4.3
- High8.8Missing Authorization to Arbitrary Plugin Deactivation/Activation
≤1.4.2Update to 1.4.3
- High8.8Authenticated (Subscriber+) Arbitrary File Upload
≤1.4.2Update to 1.4.3
Sakala: common questions
Does Sakala have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in Sakala: 3 high. At least one is not fixed in the latest version.
How do I check which version of Sakala 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 Sakala vulnerability?
59bf14a9-5abe-4b83-9364-d318eedaba83, published Jan 11, 2022: AccessPress Themes and Plugin <= Various Versions - Cross-Site Request Forgery. Severity: High (CVSS 8.8).
Is any Sakala vulnerability listed in CISA KEV?
No. None of the known Sakala vulnerabilities is currently listed in the CISA KEV catalog.
