dbcve.org
UltimateimagetoolPrestaShop extension · Advancedplugins

CVE-2024-28390

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-14
Fix available
A fix is available. Upgrade to 2.2.01 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue in Advanced Plugins ultimateimagetool module for PrestaShop before v.2.2.01, allows a remote attacker to escalate privileges and obtain sensitive information via Improper Access Control.

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 ultimateimagetool module for PrestaShop before version 2.2.01 contains an Improper Access Control vulnerability that allows remote attackers to escalate privileges and access sensitive information. The critical CVSS score of 9.8 indicates this is easily exploitable with no authentication required.

MitigationUpgrade the ultimateimagetool module to version 2.2.01 or later. Verify compatibility with the PrestaShop installation before deployment.

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
UltimateimagetoolPrestaShop extension
Affected:< 2.2.01

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 Ultimateimagetool module is installed
    Access the PrestaShop admin panel and navigate to Modules > Module Manager. Search for 'ultimateimagetool' or 'Advancedplugins' to confirm the module is present in the installation.
    Affected if the module appears in the installed modules list
  2. Determine installed module version
    In the PrestaShop admin panel, locate the Ultimateimagetool module entry and view its version information. This is typically displayed in the module details or configuration page.
    Affected if the displayed version is lower than 2.2.01
  3. Check module files for version identifier
    If admin panel access is limited, locate the module directory in the PrestaShop file structure (typically under modules/ultimateimagetool or similar). Look for a version file, composer.json, or config.xml that contains version metadata.
    Affected if the version found in the module files is 2.2.00 or earlier
  4. Verify module is enabled and accessible
    Confirm the Ultimateimagetool module status shows as enabled in the PrestaShop module manager. Since this vulnerability is exploitable without authentication, also verify the module front-end or API endpoints are publicly accessible.
    Affected if the module is enabled and exposed to unauthenticated users

A defender is affected if the Advancedplugins Ultimateimagetool module is installed and its version is below 2.2.01, with the module enabled and accessible.

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 2.2.01 or later
Fixed in 2.2.01
Interim mitigation

Upgrade the ultimateimagetool module to version 2.2.01 or later. Verify compatibility with the PrestaShop installation before deployment.

Recommended fix High confidence

2.2.01

  1. Download the ultimateimagetool module version 2.2.01 from a trusted source (official vendor or PrestaShop Addons)
  2. Log in to the PrestaShop admin panel
  3. Navigate to Modules > Module Manager
  4. Locate the installed ultimateimagetool module
  5. Click on the 'Update' or 'Upgrade' button for the module
  6. Verify the module version shows 2.2.01 after upgrade
  7. Clear PrestaShop cache via Advanced Parameters > Performance > Clear Cache
  8. Test image manipulation functionality to confirm the module works correctly after upgrade

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

Fix this in Ultimateimagetool Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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