dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-57724

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 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
Deserialization of Untrusted Data vulnerability in Themeum Kirki kirki allows Object Injection.This issue affects Kirki: from n/a through <= 6.0.12.

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 · moderate confidence

The Themeum Kirki WordPress plugin (versions up to 6.0.12) contains a deserialization vulnerability where untrusted data is passed to PHP's unserialize() function, allowing authenticated attackers to inject arbitrary PHP objects. This object injection can potentially lead to remote code execution if suitable magic methods orPOP (property-oriented programming) chains exist in the plugin or its dependencies.

MitigationUpdate the Kirki plugin to the latest version as soon as a patch is released. If no patched version is available, disable the plugin immediately and review server access logs for signs of exploitation.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Kirki plugin installation and version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate Themeum Kirki or Kirki Customizer Framework, and note the version number. Alternatively, check the plugin's main PHP file (typically in /wp-content/plugins/kirki/) for the 'Version' header in the plugin comment block.
    Affected if Kirki plugin version is 6.0.12 or lower (any version up to and including 6.0.12 is affected)
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that the Kirki plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if Plugin is active - the vulnerability requires the plugin to be loaded to be exploitable
  3. Identify if untrusted input reaches unserialize()
    Review plugin code for calls to unserialize() on user-supplied data such as $_POST, $_GET, $_REQUEST, or custom AJAX endpoints. Search the plugin directory for patterns like 'unserialize( $_POST' or 'unserialize( $' and trace whether external input flows into these calls.
    Affected if The vulnerable code path exists where $_POST/$_GET/$_REQUEST data is passed directly to unserialize() without sanitization
  4. Assess authentication requirements for the vulnerable endpoint
    Determine if the unserialize() call is protected by authentication. Check if the vulnerable code resides in an AJAX handler (wp_ajax_* or wp_ajax_nopriv_*) and whether it requires admin-level privileges or any authenticated user access.
    Affected if Any authenticated access (including subscriber-level) can trigger the vulnerability, as the CVE states authenticated attackers can exploit it

You are affected if the Kirki plugin is installed, active, and running version 6.0.12 or lower, with an active unserialize() call handling untrusted input from authenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Kirki plugin to the latest version as soon as a patch is released. If no patched version is available, disable the plugin immediately and review server access logs for signs of exploitation.

Recommended fix Moderate confidence

Kirki version 6.0.13 or later (check wordpress.org for the latest stable release)

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find the Kirki (Themeum Kirki) plugin in the list.
  5. 5. If an update is available, click 'Update Now' to update to the latest version.
  6. 6. Alternatively, you can manually download the latest version from wordpress.org or the Themeum website and upload it via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin is running version 6.0.13 or higher.
  8. 8. Test your site frontend and customizer to ensure the Kirki framework is functioning correctly.
Caveat Review the Kirki changelog for version 6.0.13 to check for any filter/hook or API changes that may affect your theme customizations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57724 — 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-57724 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