Is typo3/cms-indexed-search 11.1 vulnerable?

Composer · 2 releases from 11.1.0 to 11.1.1 · latest typo3/cms-indexed-search is 14.3.12 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. typo3/cms-indexed-search 11.1.1, the last 11.1 release, is affected by 1 known security advisory (1 medium), including CVE-2024-55923. Upgrade to 11.5.42 or later to fix all of them.

Upgrade with:composer require typo3/cms-indexed-search:^11.5.42

Is your project on an affected typo3/cms-indexed-search?

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

Advisories affecting typo3/cms-indexed-search 11.1.1

  • MediumCVE-2024-55923GHSA-7r5q-4qgx-v54514 Jan 2025

    TYPO3 Indexed Search Module vulnerable to Cross-Site Request Forgery

    Affected
    >=10.0.0 <10.4.48 · >=11.0.0 <11.5.42 · >=12.0.0 <12.4.25 · >=13.0.0 <13.4.3
    Fixed in
    10.4.48, 11.5.42, 12.4.25, 13.4.3

Every typo3/cms-indexed-search 11.1.x release

Affected: 11.1.0 to 11.1.1. Latest typo3/cms-indexed-search: 14.3.12.

VersionKnown advisories
typo3/cms-indexed-search 11.1.1CVE-2024-55923
typo3/cms-indexed-search 11.1.0CVE-2024-55923

Which of your client projects are still on typo3/cms-indexed-search 11.1?

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

Other typo3/cms-indexed-search versions

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.