Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-103065 – Broken Access Control – Kirki (WordPress Plugin) ≤ 6.3.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-103065 is a broken access control vulnerability in the Kirki WordPress plugin (developed by Themeum), caused by improper validation of specified input quantities that allows unauthenticated attackers to reach functionality that should be restricted by access control lists (ACLs). The issue affects Kirki versions through 6.3.1 and carries a CVSS v3.1 base score of 8.2 (High). It was fixed in version 6.3.2.

Technical details

  • Root cause: The plugin fails to properly validate a specified input quantity/parameter before processing a request, which is classified under CWE-1284 (Improper Validation of Specified Quantity in Input).
  • Trigger condition: An attacker sends a crafted request to a Kirki endpoint that is intended to be gated by ACL checks; because the input validation is insufficient, the ACL restriction can be bypassed.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N) — meaning the vulnerability can be exploited remotely and without authentication or victim involvement.
  • Impact: The CVSS vector indicates high confidentiality impact and low integrity impact with no availability impact (C:H/I:L/A:N), consistent with unauthorized access to functionality/data that should otherwise require proper authorization — rather than full site compromise.

Affected software

  • Kirki (WordPress Customizer/page builder plugin) by Themeum — versions up to and including 6.3.1
  • Fixed in version 6.3.2 and later

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Update the Kirki plugin to version 6.3.2 or later, which addresses the access-control and input-validation issue.
  • If immediate patching is not possible:
    • Restrict or monitor access to Kirki-related REST/AJAX endpoints at the network or WAF layer until the update can be applied.
    • Review site logs for anomalous or unauthenticated requests to Kirki plugin endpoints.
    • Limit exposure of the WordPress site’s administrative and plugin-specific endpoints where feasible.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge