dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-57680

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 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
Unauthenticated Insecure Direct Object References (IDOR) in Kirki <= 6.0.11 versions.

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

Unauthenticated IDOR vulnerability in Kirki theme customizer framework versions 6.0.11 and below allows unauthenticated attackers to access or modify sensitive objects they should not have permission to access, due to missing authorization validation on direct object references.

MitigationUpdate Kirki to a version newer than 6.0.11 if available, or implement proper authorization checks on all object references to validate user permissions before granting access.

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
None
Integrity
Low
Availability
Low

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

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. Locate the Kirki installation in your environment
    Search for the 'kirki' directory or files in your WordPress installation (typically in wp-content/themes, wp-content/plugins, or within a theme folder). Check common locations like /wp-content/themes/<theme-name>/kirki/ or look for 'kirki.php' or 'class-kirki.php' files.
    Affected if Kirki framework files are found in your WordPress installation
  2. Identify the installed Kirki version
    Open the main Kirki file (such as readme.txt, composer.json, or the primary plugin/theme file containing Kirki) and locate the version number. It is often listed in a header comment or version constant at the top of the file.
    Affected if The version string shows a number equal to or lower than 6.0.11
  3. Confirm the customizer framework is active
    Access your WordPress admin dashboard and navigate to Appearance > Customize. Verify that the customizer interface loads and that Kirki controls or panels are present and functional.
    Affected if The WordPress customizer loads with Kirki-specific controls or panels visible
  4. Test for unauthenticated object access
    Send a direct HTTP request to your site's customizer AJAX endpoints or API routes that handle object references (such as post IDs, option names, or setting keys) without providing authentication credentials. Observe whether the request is processed without returning a 401 or 403 error.
    Affected if Unauthenticated requests to customizer-related endpoints return successful responses instead of authorization errors

Your environment is affected if the Kirki framework is installed and the installed version is 6.0.11 or lower, exposing unauthenticated IDOR vulnerabilities in the customizer.

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 Kirki to a version newer than 6.0.11 if available, or implement proper authorization checks on all object references to validate user permissions before granting access.

Recommended fix Moderate confidence

Kirki > 6.0.11 (latest available version)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Kirki plugin in the list
  4. 4. Check the current installed version of Kirki
  5. 5. If the installed version is 6.0.11 or lower, update to the latest available version of Kirki
  6. 6. Alternatively, download the latest Kirki version from the official WordPress repository or the developer's website
  7. 7. Update the plugin and verify the new version is installed

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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