typo3/cms-frontend vulnerabilities

TYPO3 CMS Frontend

Registry
Composer
Latest
14.3.12
License
GPL-2.0-or-later

4 known advisories

The latest version, 14.3.12, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require typo3/cms-frontend:^14.3.12

Is your project on an affected typo3/cms-frontend?

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

Security advisories for typo3/cms-frontend

  • LowCVE-2010-5097GHSA-9hw3-4gvp-8mv517 May 2022

    TYPO3 Cross-site scripting (XSS) vulnerability in the click enlarge functionality

    Affected
    >=4.3.0 <4.3.9 · >=4.4.0 <4.4.5
    Fixed in
    4.3.9, 4.4.5
  • LowCVE-2010-5098GHSA-3mqf-fwc6-vwqw17 May 2022

    TYPO3 Cross-site scripting (XSS) vulnerability in the FORM content object

    Affected
    >=4.2.0 <4.2.16 · >=4.4.0 <4.4.5 · >=4.3.0 <4.3.9
    Fixed in
    4.2.16, 4.3.9, 4.4.5
  • MediumCVE-2010-3670GHSA-3276-p9f2-8q8921 Apr 2022

    TYPO3 is vulnerable to insecure randomness during hash generation in forgot password function

    Affected
    <4.3.4 · >=4.4.0 <4.4.1
    Fixed in
    4.3.4, 4.4.1
  • MediumCVE-2010-3667GHSA-48ww-8h7g-4hwq21 Apr 2022

    TYPO3 is vulnerable to Spam Abuse in the native form content element

    Affected
    <4.1.14 · >=4.2.0 <4.2.13 · >=4.3.0 <4.3.4 · >=4.4.0 <4.4.1
    Fixed in
    4.1.14, 4.2.13, 4.3.4, 4.4.1

Is your typo3/cms-frontend version vulnerable?

Which of your client projects still run an old typo3/cms-frontend?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.