CVE-2026-57627
Deferred Deferred - Pending Action

Subscriber Server Side Request Forgery in Kirki <= 6.0.11

Vulnerability report for CVE-2026-57627, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-26

Last updated on: 2026-06-26

Assigner: Patchstack

Description

Subscriber Server Side Request Forgery (SSRF) in Kirki <= 6.0.11 versions.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-26
Last Modified
2026-06-26
Generated
2026-07-16
AI Q&A
2026-06-26
EPSS Evaluated
2026-07-15
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wordpress kirki to 6.0.12 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The WordPress Kirki Plugin, versions 6.0.11 and below, is vulnerable to a Server Side Request Forgery (SSRF) attack.

This means an attacker can make the affected website send arbitrary requests to other domains, potentially abusing the server to access internal or external resources.

The vulnerability has a low severity impact with a CVSS score of 4.9 and is classified under OWASP Top 10 A10: Server-Side Request Forgery (SSRF).

Detection Guidance

To detect the Kirki SSRF vulnerability on your system, you should first verify the version of the Kirki plugin installed on your WordPress site. Versions 6.0.11 and below are vulnerable.

Since this is a Server Side Request Forgery vulnerability, monitoring outgoing HTTP requests from your server to unexpected or unauthorized domains can help identify exploitation attempts.

You can check the Kirki plugin version by running the following WP-CLI command:

  • wp plugin list --status=active | grep kirki

To detect suspicious outgoing requests, you can use network monitoring tools or commands such as:

  • tcpdump -i any -nn port 80 or port 443
  • netstat -anp | grep ESTABLISHED

Additionally, reviewing web server logs for unusual outbound request patterns or unexpected URLs can help identify SSRF exploitation.

Ultimately, the recommended action is to update the Kirki plugin to version 6.0.12 or later to patch the vulnerability.

Impact Analysis

An attacker exploiting this vulnerability could make the affected website send unauthorized requests to other domains.

This could lead to exposure of sensitive internal information or unauthorized interactions with internal services.

The impact is considered low severity but could still compromise confidentiality and integrity of data accessible through the server.

Compliance Impact

The vulnerability allows attackers to make arbitrary requests from the affected website to other domains, potentially exposing sensitive internal information.

Exposure of sensitive internal information due to this SSRF vulnerability could lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require safeguarding sensitive data against unauthorized access.

Therefore, if exploited, this vulnerability may impact compliance with common standards and regulations by risking unauthorized data exposure.

Mitigation Strategies

The vulnerability in the WordPress Kirki Plugin versions 6.0.11 and below can be mitigated by updating the plugin to version 6.0.12 or later.

If updating immediately is not possible, it is recommended to seek assistance from a hosting provider or a web developer to help mitigate the risk.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57627. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart