p PatchFirst

PatchFirst · Latest vulnerabilities

typo3/cms-backend vulnerabilities · Page 2

Vulnerabilities published for typo3/cms-backend in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 25

  1. CVE-2009-3631

    Not ratedEPSS 2.94%Fix available

    CVE-2009-3631

    The Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2, when the DAM extension or ftp upload is enabled, allows remote authenticated users to execute arbitrary commands via shell metacharacters in a filename.

    • Update to 4.1.13
    • Update to 4.2.10
    • Update to 4.3beta2
    Published Updated
  2. CVE-2009-3630

    Not ratedEPSS 1.98%Fix available

    CVE-2009-3630

    The Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2 allows remote authenticated users to place arbitrary web sites in TYPO3 backend framesets via crafted parameters, related to a "frame hijacking" issue.

    • Update to 4.1.13
    • Update to 4.2.10
    • Update to 4.3beta2
    Published Updated
  3. CVE-2009-3629

    Not ratedEPSS 1.54%Fix available

    CVE-2009-3629

    Multiple cross-site scripting (XSS) vulnerabilities in the Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2 allow remote authenticated users to inject arbitrary web script or HTML via unspecified vectors.

    • Update to 4.1.13
    • Update to 4.2.10
    • Update to 4.3beta2
    Published Updated
  4. CVE-2009-3628

    Not ratedEPSS 1.13%Fix available

    CVE-2009-3628

    The Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2 allows remote authenticated users to determine an encryption key via crafted input to a tt_content form element.

    • Update to 4.1.13
    • Update to 4.2.10
    • Update to 4.3beta2
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →