CVE-2026-102173 themeum CVE debrief

Who should care

Defenders responsible for WordPress installations using the Kirki plugin, particularly those with public user registration enabled and published pages carrying a `kirki-register` element, should assess exposure and prioritize verification and patching.

Why it matters

The Kirki plugin vulnerability allows unauthenticated attackers to inject arbitrary web scripts, potentially leading to Cross-Site Scripting attacks. Defenders should prioritize verification, patching, and monitoring to prevent exploitation.

• Assess and verify exposure in your environment
• Prioritize patching to prevent potential exploitation
• Monitor for potential exploitation attempts
• Verify public user registration is necessary and consider disabling it if not required

Technical summary

The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via registration metadata in all versions up to, and including, 6.3.1. This is due to insufficient escaping in `ExceptionalElements::image_element()`, which concatenates a user-meta value straight into an `<img src=` attribute, allowing unauthenticated attackers to inject arbitrary web scripts that execute when a user accesses a page rendering a Kirki users collection with an image element bound to one of nine registration meta fields. The vulnerability requires public user registration to be enabled and a published page with a `kirki-register` element

Defensive priority

Defenders should prioritize verifying and updating to a patched version of the Kirki plugin, assessing exposure in their environment, and monitoring for potential exploitation attempts.

Recommended defensive actions

• Verify and update to a patched version of the Kirki plugin
• Assess exposure in your environment
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to code snippets and patches. The vulnerability exists in the Kirki plugin's handling of user registration metadata, specifically in the `ExceptionalElements::image_element()` function. The function concatenates user-meta values into an `<img src=` attribute without proper escaping, allowing for stored cross-site scripting (XSS) attacks. The CVE record and source item also note that public user registration

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.