CVE-2020-13459
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 · uneditedAn issue was discovered in the Image Resizer plugin before 2.0.9 for Craft CMS. There is stored XSS in the Bulk Resize 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 · high confidenceA stored cross-site scripting (XSS) vulnerability exists in the Image Resizer plugin for Craft CMS. The vulnerability is present in the Bulk Resize action, allowing attackers to inject malicious JavaScript code that persists on the server and executes when other users view affected content.
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< 2.0.9CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Image Resizer plugin is installedAccess the Craft CMS plugin management interface and confirm the Verbb Image Resizer plugin is listed among installed plugins.Affected if The plugin is installed and listed in the control panel.
-
Check the installed version numberIn the plugin management area, view the installed version of Verbb Image Resizer. Compare this version against the affected range of versions prior to 2.0.9.Affected if The installed version is any version prior to 2.0.9 (e.g., 2.0.8, 2.0.7, 2.0.6, etc.).
-
Confirm Bulk Resize functionality is accessibleNavigate to the Image Resizer plugin settings or locate the Bulk Resize action within the Craft CMS control panel. Determine whether this feature has been configured or used.Affected if The Bulk Resize feature exists and is accessible in the control panel.
-
Inspect stored Bulk Resize configurations for suspicious contentExamine any saved Bulk Resize presets, settings, or configurations in the plugin database or configuration files. Look for unexpected script tags, JavaScript event handlers, or encoded payloads.Affected if Any Bulk Resize configuration contains script tags, javascript: URIs, or other XSS payloads in fields that accept user input.
The environment is affected if the installed Image Resizer plugin version is below 2.0.9 and the Bulk Resize feature is accessible or has been used.
Generated from the published advisory. Verify against your own configuration.
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 data2.0.9
Update the Image Resizer plugin to version 2.0.9 or later to patch the stored XSS vulnerability. As a secondary measure, implement output encoding when rendering user-supplied content in the Bulk Resize functionality.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13459 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-13459 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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