Skip to main content

Kirki EUVDEUVD-2026-95577

| CVE-2026-84224 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-10-09 WPScan GHSA-w2rx-5q64-f3mg
4.1
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain editor-level WordPress account
  2. Delivery
    Submit crafted URL to Kirki fetch feature
  3. Exploit
    Server issues request to internal target
  4. Execution
    Observe response/timing differences
  5. Impact
    Enumerate live internal services

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated account with editor-level privileges or above (CVSS PR:H), so this is not remotely exploitable by anonymous users. The specific trigger is Kirki's URL-fetching functionality, which does not validate the host of a supplied URL before requesting it; an attacker abuses that feature to make the WordPress server issue outbound requests to internal services it can reach but external users cannot. Limiting factors: the plugin version must be before 6.3.2, the attacker must hold a trusted privileged role (significantly narrowing the realistic attacker set to insiders or compromised privileged credentials), and the impact is confined to confidentiality - specifically inferring which internal hosts/services are live from responses - with no write or denial capability.

Impact

This is a server-side request forgery (SSRF) / internal host-enumeration issue in the Kirki WordPress plugin, and the signals converge on it being a modest, not urgent, priority. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N, base 4.1 / Medium) tells a consistent story: network-reachable and low-complexity, but gated behind high privileges (PR:H) and limited to low confidentiality impact with no integrity or availability effect - the scope change (S:C) reflects that the forged requests reach internal services beyond the web application's own authorization boundary. The description aligns cleanly with this vector (editor-level-and-above access, requests to otherwise-unreachable internal services, ability to infer which are live), so there is no attack-vector-versus-description conflict here. On exploitation signals, publicly available exploit code exists (POC via WPScan), but there is NO CISA KEV listing and NO EPSS score was provided in the input, so there is no evidence of active, widespread exploitation - POC availability must not be conflated with in-the-wild use. The key limiting factor is the PR:H requirement: an attacker must already hold a trusted editor/admin-class account, which greatly narrows the realistic threat to insiders, compromised privileged credentials, or multi-stage attacks. Net assessment: a legitimate medium-severity bug worth patching on a normal cycle, not a high-urgency emergency - primarily useful as an internal reconnaissance primitive rather than a direct path to system compromise.

Exploit ScenarioDerived

An attacker who has obtained (or abused) an editor-or-higher WordPress account supplies a crafted URL pointing at an internal address (for example a cloud metadata endpoint or an internal admin service) to a Kirki feature that fetches remote URLs without host validation. The site issues the request on the attacker's behalf, and differences in the response or timing reveal which internal hosts and ports are alive, enabling internal network mapping from the outside. Public exploit code for this issue is available via WPScan.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 09, 2026

Server-side request forgery in the Kirki WordPress plugin before 6.3.2 allows authenticated users holding editor-level privileges or above to supply a URL that the WordPress server then fetches without validating the target host, letting them probe internal-only services and infer from the responses which of those hosts are live. The issue is rated CVSS 4.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N), so impact is confined to information disclosure with no write, code execution, or denial-of-service capability, and exploitation requires a trusted privileged account rather than anonymous access. Publicly available exploit code exists and WPScan is credited as the reporting source, but there is no CISA KEV confirmation of active exploitation; combined with the high privilege prerequisite, the signals converge on a modest, non-urgent priority appropriate for routine patching alongside other plugin updates.

RemediationAI

Upgrade the Kirki plugin to version 6.3.2 or later - the vendor-released patch is the fixed 6.3.2 release, referenced by the WPScan advisory at https://wpscan.com/vulnerability/6a2455dd-8da9-4c7e-a249-3c694cf2983e/; sites that receive Kirki via a bundled theme must confirm the theme ships the updated plugin rather than assuming it. Because exploitation requires an editor-level or higher account, reduce the attack surface by auditing and trimming privileged accounts (removing stale or unnecessary Editor/Administrator users) and enforcing least privilege and strong authentication, accepting that this limits legitimate editorial workflows. Apply outbound egress filtering on the WordPress host - deny requests from the web server to RFC1918/private ranges and to internal-only hostnames - which neutralizes the SSRF probe but risks breaking unrelated plugins and features that legitimately call internal endpoints. If the URL-fetch feature is not required, disabling that plugin functionality is a lower-risk alternative to broad egress blocking; keep in mind it may break theme or site-builder features and should be tested. Detection should focus on outbound requests originating from the web tier to private address space, and because publicly available exploit code exists but active exploitation is not confirmed via CISA KEV, treat this as a scheduled patch rather than an emergency response.

Affected VersionsENISA

Kirki 0 <6.3.2

Affected Packages

euvd kirki fix: 6.3.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The underlying weakness is server-side request forgery (SSRF) in the URL-fetching functionality of the Kirki WordPress plugin, a popular toolkit used by themes and site builders. The plugin accepts a caller-supplied URL and performs an outbound HTTP request without validating the host, so the request originates from the WordPress server's network position rather than the attacker's, which is how otherwise unreachable internal services become observable. The provided record carries no CWE assignment, but the behavior corresponds to the SSRF class (CWE-918); the CVSS vector's scope-change flag (S:C) reflects that the vulnerable WordPress component affects resources in a different security authority - the internal services being probed - while the C:L metric confirms that only confidentiality of live-host information is exposed. The CPE string cpe:2.3:a:unknown:kirki:*:*:*:*:*:*:*:* indicates that the affected product is Kirki with an unmapped vendor namespace, so version-based detection should rely on the plugin directory version rather than a reliable vendor CPE.

Know when Kirki gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 4.1 MEDIUM
AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
vuln.today AI 4.1 MEDIUM

Network-reachable, low-complexity SSRF requiring a privileged editor+ account (PR:H); scope changes (S:C) as requests reach internal services, yielding only low confidentiality (C:L) and no integrity/availability impact.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Oct 09, 2026 - 10:16 EUVD
CVE Published
Oct 09, 2026 - 08:06 cve.org
MEDIUM 4.1

DescriptionCVE.org

The Kirki WordPress plugin before 6.3.2 does not validate the host of a URL it is given before fetching it, allowing users with editor-level access and above to make the site issue requests to internal services that are not otherwise reachable, and to tell which of those are live from the response.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
popular WordPress theme customizer framework, broad but not universal footprint
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +20
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

More in Kirki

View all
CVE-2026-13147 CRITICAL POC
9.1 Jul 20

Server-Side Request Forgery in the Kirki WordPress plugin before 6.0.12 allows unauthenticated attackers to coerce the s

CVE-2026-12721 HIGH POC
8.6 Jul 31

SQL injection in the Kirki WordPress plugin before version 6.0.13 enables unauthenticated remote attackers to read arbit

CVE-2026-12720 HIGH POC
7.5 Jul 31

PHP Object Injection in the Kirki WordPress plugin before 6.0.13 enables a two-stage attack where unauthenticated users

CVE-2026-84219 HIGH POC
7.5 Sep 06

Stored cross-site scripting in the Kirki WordPress plugin before 6.3.0 allows unauthenticated remote attackers to persis

CVE-2026-74992 MEDIUM POC
6.8 Aug 20

Arbitrary file upload via malformed archive in the Kirki WordPress customizer plugin (all versions before 6.2.3) allows

CVE-2026-84223 MEDIUM POC
6.8 Sep 20

Stored cross-site scripting in the Kirki WordPress plugin affects versions 6.0.0 through 6.3.0, which allow SVG files to

CVE-2026-84221 MEDIUM POC
6.8 Sep 05

SQL injection in the Kirki WordPress plugin (versions 6.0.0 through <6.3.0) enables authenticated users with editor-leve

CVE-2026-16747 MEDIUM POC
6.5 Aug 12

Unauthenticated shortcode injection in Kirki WordPress plugin (all versions before 6.2.1) allows any remote attacker to

CVE-2026-57724 CRITICAL
9.8 Jul 13

Object injection in the Themeum Kirki WordPress customizer framework (all versions through 6.0.12) allows attackers to a

CVE-2026-77754 MEDIUM POC
5.3 Aug 26

Kirki WordPress Customizer Framework plugin before 6.0.14 exposes registered user email addresses, comment author emails

CVE-2026-84222 MEDIUM POC
5.3 Sep 09

Unauthenticated content disclosure in the Kirki WordPress plugin before 6.3.0 allows any remote attacker to retrieve the

CVE-2026-12723 MEDIUM POC
5.3 Jul 20

Unauthenticated comment manipulation in the Kirki WordPress plugin (versions before 6.0.12) allows remote attackers to o

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy