dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4804

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Zakra WordPress theme registers three post meta fields (zakra_menu_item_color, zakra_menu_item_hover_color, zakra_menu_item_active_color) with REST API exposure but no sanitize_callback. The REST API path bypasses the sanitize_hex_color() protection used by the classic editor. Unsanitized meta values are retrieved via get_post_meta() and concatenated into CSS strings output through wp_add_inline_style() without escaping, enabling stored XSS.

MitigationUpdate to a patched version of Zakra theme (4.2.1 or later); alternatively, remove the REST API exposure or add sanitize_callback to the affected register_post_meta() calls and escape values before CSS output.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Zakra theme version
    In WordPress admin, go to Appearance > Themes and check the installed Zakra theme version. Alternatively, inspect the style.css file in wp-content/themes/zakra/ and look for the 'Version:' header.
    Affected if Version is lower than 4.2.1 (the patched version)
  2. Verify REST API meta exposure exists
    Make a GET request to /wp-json/wp/v2/posts/<post_id> and check if the response includes the meta fields zakra_menu_item_color, zakra_menu_item_hover_color, or zakra_menu_item_active_color in the 'meta' object.
    Affected if These meta fields appear in the REST API response without requiring authentication or special capability checks
  3. Inspect register_post_meta calls
    In the theme files (typically in functions.php or includes files), locate calls to register_post_meta() for the three affected fields. Check if the 'sanitize_callback' argument is missing or set to an ineffective value.
    Affected if register_post_meta calls for zakra_menu_item_color, zakra_menu_item_hover_color, or zakra_menu_item_active_color lack a proper sanitize_callback function
  4. Check CSS output for escaping
    Search the theme source code for wp_add_inline_style() calls that use get_post_meta() to retrieve the three affected meta fields. Inspect whether the retrieved values are escaped (e.g., via esc_attr, esc_html) before CSS concatenation.
    Affected if get_post_meta() values for the affected fields are concatenated into CSS strings without escaping before being passed to wp_add_inline_style()
  5. Test meta write via REST API
    Send a POST request to /wp-json/wp/v2/posts/<post_id> with a meta object containing one of the affected fields set to a value containing JavaScript (e.g., 'red}body{background:url(javascript:alert(1))'). Then request the post via REST API or view the frontend to see if the unsanitized value appears in an inline style tag.
    Affected if The unsanitized meta value appears in the page source within a <style> tag (indicating wp_add_inline_style usage) without proper escaping

A site is affected if it uses Zakra theme version lower than 4.2.1 and has the REST API enabled, allowing unauthenticated or low-privilege users to write post meta values that get output as unescaped CSS via wp_add_inline_style().

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of Zakra theme (4.2.1 or later); alternatively, remove the REST API exposure or add sanitize_callback to the affected register_post_meta() calls and escape values before CSS output.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4804 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4804 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data