HomeWordPress vulnerabilitiesZakra
Zakra vulnerabilities
Zakra has 2 known vulnerabilities in this database. The most recent published record is dated 3 Jul 2026.
- Known vulnerabilities
- 2
- Active installs
- 30,000+
- Latest version
- 4.3.3
- Last updated
- 16 Sep 2026
- Most recent
- 3 Jul 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-4804 | Medium 6.4 | Up to 4.2.0 | Fixed in a later version (latest 4.3.3) | 3 Jul 2026 |
| Broken access control CVE-2025-8595 | Medium 4.3 | Up to 4.1.5 | Fixed in a later version (latest 4.3.3) | 6 Aug 2025 |
Read the published descriptions
- CVE-2026-4804, 3 Jul 2026
- The Zakra theme for WordPress is vulnerable to Stored Cross-Site Scripting via post meta values in all versions up to, and including, 4.2.0. This is due to the theme registering three post meta fields (zakra_menu_item_color, zakra_menu_item_hover_color, and zakra_menu_item_active_color) with 'show_in_rest' => true and 'auth_callback' => '__return_true', but without any sanitize_callback parameter in the register_post_meta() calls. While the classic editor save path applies sanitize_hex_color() sanitization, the REST API path completely bypasses this protection. The unsanitized meta values are then retrieved via get_post_meta() and concatenated directly into CSS strings that are output through wp_add_inline_style() without any escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the injected page. CVE record
- CVE-2025-8595, 6 Aug 2025
- 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 record
What to do if you run Zakra
If you run Zakra, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Zakra vulnerabilities
Free. We email you when a new vulnerability is published for Zakra, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.