dbcve.org
Kraken.io Image OptimizerWordPress extension · Kraken

CVE-2023-0619

MEDIUM · 6.5 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to after 2.6.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Kraken.io Image Optimizer plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on its AJAX actions in versions up to, and including, 2.6.8. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to reset image optimizations.

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

The Kraken.io Image Optimizer WordPress plugin versions up to 2.6.8 lack proper capability checks on AJAX action handlers, allowing any authenticated user with subscriber-level permissions or higher to reset image optimizations through AJAX endpoints that should be restricted to administrators.

MitigationUpdate the plugin to version 2.6.9 or later which includes proper capability checks, or manually add current_user_can() authorization verification to all AJAX action callbacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Kraken.io Image OptimizerWordPress extension
Affected:<= 2.6.8

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

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

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. Confirm Kraken.io Image Optimizer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Kraken.io Image Optimizer' or check the wp-content/plugins directory for the kraken-image-optimizer folder
    Affected if Plugin is not found in the WordPress installation
  2. Identify installed plugin version
    In Plugins page, click 'View Details' on Kraken.io Image Optimizer to see the version number, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if Version is 2.6.8 or lower
  3. Verify AJAX endpoint capability checks
    Examine the main plugin PHP file (e.g., kraken.php) and look for add_action('wp_ajax_...') calls. Check each AJAX callback function for a current_user_can() or similar capability check before executing logic. Vulnerable code will lack this check.
    Affected if AJAX handlers do not contain current_user_can() or equivalent authorization checks before processing requests
  4. Confirm existence of subscriber-level or higher non-admin users
    In WordPress admin, go to Users > All Users and check if any users exist with the Subscriber, Contributor, Author, or Editor roles (users who are not Administrators)
    Affected if Non-admin authenticated users exist and the plugin version is vulnerable

A user is affected if the Kraken.io Image Optimizer plugin version is 2.6.8 or lower AND the site has any authenticated users with subscriber-level or higher permissions, since the vulnerable AJAX endpoints would be accessible to them without proper authorization checks.

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
Upgrade available Upgrade to a release after 2.6.8
Interim mitigation

Update the plugin to version 2.6.9 or later which includes proper capability checks, or manually add current_user_can() authorization verification to all AJAX action callbacks.

Recommended fix Moderate confidence

Kraken.io Image Optimizer version 2.6.9 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Kraken.io Image Optimizer plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. 6. After updating, verify that the new version is >= 2.6.9

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

Fix this in Kraken.io Image Optimizer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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