Image ResizerApplication · Verbb

CVE-2020-13458

HIGH · 8.8 CVSS v3.1 Published 2020-05-25
Fix available
A fix is available. Upgrade to 2.0.9 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
An issue was discovered in the Image Resizer plugin before 2.0.9 for Craft CMS. There are CSRF issues with the log-clear controller action.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Image Resizer plugin for Craft CMS allows attackers to trigger the log-clear controller action without proper CSRF token validation, potentially allowing unauthorized log clearing via malicious requests.

MitigationUpdate Image Resizer plugin to version 2.0.9 or later which includes CSRF protection, or disable the plugin if not needed.

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
Image ResizerApplication
Affected:< 2.0.9

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Image Resizer plugin is installed
    Access your Craft CMS admin panel and navigate to Settings > Plugins, or inspect your craft/plugins or vendor/verbb/image-resizer directory to verify the Image Resizer plugin is present in the installation.
    Affected if The plugin is not listed or the directory does not exist, then you are not affected.
  2. Identify installed Image Resizer version
    In Craft CMS admin panel, go to Settings > Plugins and click on the Image Resizer entry to view its version number. Alternatively, check the composer.json file in vendor/verbb/image-resizer for the installed version.
    Affected if The installed version is lower than 2.0.9, indicating you are running a vulnerable version.
  3. Verify Craft CMS version
    Navigate to Settings > General in your Craft CMS admin panel to confirm the CMS version. The Image Resizer plugin runs on top of Craft CMS.
    Affected if This step confirms the environment context; the vulnerability exists regardless of Craft CMS version, but ensure your Craft installation is also up to date.
  4. Check if log-clear action is accessible
    Attempt to access the log-clear endpoint directly or inspect your routes configuration. The vulnerable endpoint is typically at /actions/image-resizer/logs/clear or similar paths under the image-resizer controller.
    Affected if The endpoint responds without requiring CSRF token validation, confirming the vulnerability is exploitable in your environment.
  5. Review CSRF token configuration
    In your Craft CMS general settings, verify whether CSRF protection is enabled. The vulnerability exists because the plugin does not validate CSRF tokens, so even if CSRF is enabled in Craft, the plugin may not be using it properly.
    Affected if CSRF protection is enabled in Craft but the Image Resizer plugin does not implement token validation for the log-clear action.

You are affected if the Verbb Image Resizer plugin is installed with a version lower than 2.0.9 and the log-clear functionality is accessible without CSRF token validation.

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.

From vendor data
Upgrade available Upgrade to 2.0.9 or later
Fixed in 2.0.9
Interim mitigation

Update Image Resizer plugin to version 2.0.9 or later which includes CSRF protection, or disable the plugin if not needed.

Fix this in Image Resizer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13458 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2020-13458 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