Zakra: A security weakness
Zakra is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Zakra
- Plugin slug
zakra- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Aug 06, 2025
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Aug 06, 2025 and is one of 2 known issues for this theme.
Update, patch or deactivate.
No fixed release is identified. Update Zakra when a confirmed fixed release becomes available; until then, disable and remove it when the site's risk warrants.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Zakra theme for WordPress is vulnerable to unauthorized data modification due to a missing capability check on the welcome_notice_import_handler() function in all versions up to, and including, 4.1.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to import demo settings.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N