Is oxid-esales/smarty-component 1.0 vulnerable?

Composer · 2 releases from 1.0.0 to 1.0.1 · latest oxid-esales/smarty-component is 1.0.1 · checked 18 Nov 2026

No known advisories in the last release

oxid-esales/smarty-component 1.0.1, the last 1.0 release, has no known advisories. 1 advisory affects earlier 1.0.x releases, so update to 1.0.1.

Update within 1.0:composer require oxid-esales/smarty-component:^1.0.1

Is your project on an affected oxid-esales/smarty-component?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.0.x, affecting earlier releases

  • HighCVE-2024-56526GHSA-qqcr-9jfc-35c413 May 2025

    OXID eShop May Display User Information

    Affected
    <1.0.1
    Fixed in
    1.0.1

Every oxid-esales/smarty-component 1.0.x release

Affected: 1.0.0. 1.0.1 is not affected.

VersionKnown advisories
oxid-esales/smarty-component 1.0.1None
oxid-esales/smarty-component 1.0.0CVE-2024-56526

Which of your client projects are still on oxid-esales/smarty-component 1.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact oxid-esales/smarty-component version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.