Skip to content
OpenAdvisories

Vendor

TYPO3

198 known vulnerabilities.

198 results · Feed

  • Medium 6.0

    Broken Access Control in extension "femanager" (femanager)

    The extension fails to restrict which frontend usergroups a logged-in user may assign to their own account when the profile edit plugin uses its default field configuration, allowing self-service privilege escalation into arbitrary frontend groups.

  • High 8.2

    Information Disclosure in extension "femanager" (femanager)

    The extension's user detail view fails to verify that a requested user record matches the configured or logged-in target, allowing any visitor with access to the Detail or List plugin to retrieve another frontend user's profile data, including name, email, da…

  • High 8.3

    Broken Access Control in extension "femanager" (femanager)

    The extension fails to require the dedicated admin confirmation token when processing an admin-approval request, so a regular user confirmation hash, obtainable by any visitor through the public resend-confirmation action, is sufficient to self-approve a pend…

  • Critical 9.5

    Server-Side Template Injection in extension "powermail" (powermail)

    The extension passes the raw value of a form field configured as "This field contains the name of the sender" directly into a Fluid View as template source, without any sanitization, and renders it. An anonymous, unauthenticated user can submit Fluid template…

  • Critical 9.3

    Remote Code Execution in extension "HTML5 Video Player vs. Powermail" (html5videoplayer_powermail)

    The extension fails to safely process untrusted client input of an attacker-controlled cookie directly to PHP's unserialize(). A remote, unauthenticated attacker can supply a crafted serialized payload to trigger PHP Object Injection, leading to Remote Code E…

  • High 7.7

    SQL Injection in extension "Forms Export" (frp_form_answers)

    The extension fails to properly sanitize user input before using it in a database query. As a result, a low-privileged backend user can inject arbitrary SQL through a URL parameter within the "Forms Export" backend module. Exploitation requires a low-privileg…

  • Medium 6.0

    Path Traversal in extension "Mask" (mask)

    The extension fails to validate a client-supplied template element key before using it to build file paths for saving and deleting Mask template files. An authenticated backend user with access to the Mask module can supply a key containing path traversal seq…

  • High 8.7

    Broken Access Control in extension "Telephone Directory" (telephonedirectory)

    The extension validates the HMAC of a frontend employee edit link only in the action that renders the edit form, not in the action that persists the change. An unauthenticated visitor who knows the UID of a visible employee record can send a direct POST reque…

  • High 8.8

    Broken Access Control in extension "Club Directory" (clubdirectory)

    The extension resolves the targeted club record from a user-supplied request argument in its frontend edit, update, and activate actions, but performs no ownership check in any of them. An unauthenticated visitor who knows the UID of a club record can send a …

  • High 8.8

    Broken Access Control in extension "Industry Directory" (yellowpages2)

    The frontend company self-service editing feature relies on a template-level visibility flag to hide the edit form for company records a visitor does not own, but the corresponding write operation does not repeat this ownership check on the server side. As a …

  • High 8.8

    Broken Access Control in extension "Forum" (pforum)

    The frontend topic editing flow does not verify on the server side that the requesting visitor owns the topic being modified. As a result, a visitor who knows the identifier of a topic from the public forum can submit a modified update request for that topic …

  • High 7.1

    Broken Access Control in extension "Events 2" (events2)

    The frontend management plugin attributed a newly created event to the submitting user's organizer record only when the request supplied no organizer of its own. The accompanying permission check confirmed only that the submitting user held any organizer role…

  • High 7.1

    Broken Access Control in extension "Events 2" (events2)

    The permission check for the frontend management update flow verified a different event than the one the request went on to modify. A user with frontend event management access could therefore modify events belonging to other organizers.

  • High 8.3

    Broken Access Control in extension "femanager" (femanager)

    The extension's invitation controller fails to stop processing after redirecting on invalid input (missing hash, non-existent, disabled, or deleted users), allowing an unauthenticated attacker to set a new password for and re-enable an arbitrary existing fron…

  • High 7.3

    TYPO3 CMS - Broken Access Control in Backend and Install Tool

    The referrer enforcement introduced with TYPO3-CORE-SA-2020-006 (CVE-2020-11069) became ineffective in TYPO3 v13.0, where TYPO3 CMS started serving the backend and Install Tool applications from the site's main entry script instead of the dedicated typo3/ dir…

  • Medium 6.3

    TYPO3 CMS - Unrestricted File Upload in Form Framework

    Users were able to upload files with arbitrary MIME types to forms using FileUpload or ImageUpload elements with allowedMimeTypes configured. The restriction was not enforced server-side because the MimeTypeValidator was registered during form building before…

  • High 7.1

    TYPO3 CMS - Broken Access Control in Media Module

    Backend users with file download permissions were able to download files from the fallback storage of the file abstraction layer (FAL) via the Media Module. Since the fallback storage resolves paths relative to the server's document root, this could expose se…

  • High 8.7

    TYPO3 CMS - Privilege Escalation & SQL Injection in Form Framework

    Backend users with write access to the form_definition database table were able to directly create, update, or delete form definition records via DataHandler, bypassing the Form Framework's persistence validation and permission checks. This allowed injecting …

  • Medium 6.3

    TYPO3 CMS - Insecure Deserialization in Core API

    TYPO3's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation or class restrictions. An attacker with write access to the underlying storage backend (cache store or sys_registry data…

  • Low 2.1

    TYPO3 CMS - Broken Access Control in File Abstraction Layer

    The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the projec…

  • Medium 5.3

    TYPO3 CMS - Broken Access Control in Backend API

    Authenticated backend users were able to retrieve file metadata via several Backend API routes without proper permission checks, allowing access to files outside their permitted file mounts or storages. This issue affects TYPO3 CMS versions before 10.4.57, 11…

  • Medium 5.3

    TYPO3 CMS - Broken Access Control in Clipboard

    Backend users were able to insert arbitrary records and files into the TYPO3 clipboard without proper read permission checks, which allowed users to gather information about records and files they were not authorized to view. This issue affects TYPO3 CMS vers…

  • Medium 5.3

    TYPO3 CMS - Broken Access Control in DataHandler

    Backend users were able to move records to a different page without having edit permissions on the source page. This issue affects TYPO3 CMS versions 13.0.0-13.4.30 and 14.0.0-14.3.2.

  • Medium 5.3

    TYPO3 CMS - Broken Access Control in Recycler

    Backend users with access to the Recycler module were able to restore soft-deleted records on pages or for tables they were not authorized to modify. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0…

  • Medium 5.1

    TYPO3 CMS - Cross-Site Scripting in Indexed Search

    Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. When displayed in frontend search results via the Indexed Search plugin, these titles were rendered…

  • Medium 5.3

    TYPO3 CMS - Open Redirect in Core Utilities

    Applications that use GeneralUtility::sanitizeLocalUrl to allow only local URLs are vulnerable to open redirect attacks if the URL is used after it has passed the aforementioned sanitization checks. This enables attackers to redirect users to external content…

  • High 7.6

    TYPO3 CMS - Broken Access Control in Form Framework

    Backend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., .FORM.YAML) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL…

  • High 7.2

    TYPO3 CMS - Destructive Actions on File Mount Folders

    Non-privileged backend users with file mount access were able to perform write operations (move, delete, rename) on folders representing the root of an active file mount due to missing authorization restrictions. This issue affects TYPO3 CMS versions before 1…

  • High 7.6

    TYPO3 CMS - Broken Access Control in Form Framework

    Backend users with access to the Form Framework were able to use files not ending in .form.yaml as form definitions, which were processed without denying the incorrect file extension. Maliciously crafted form definition files can be used to execute arbitrary …

  • Medium 5.1

    TYPO3 HTML Sanitizer allows Cross-Site Scripting

    Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.

  • Low 2.1

    TYPO3 HTML Sanitizer allows Cross-Site Scripting

    When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-sit…

  • Critical 9.2
    CVE-2026-46725 Scanner template

    Remote Code Execution in extension "Content Element Selector" (ceselector)

    The extension passes an attacker-controlled cookie directly to PHP's unserialize() without safely processing the input. A remote, unauthenticated attacker can supply a crafted serialized payload to trigger PHP Object Injection, leading to Remote Code Executio…

  • High 8.2

    SQL Injection in extension "Address List" (tt_address)

    The AddressRepository::getSqlQuery() method constructs a database query without properly sanitizing user input, leading to SQL Injection. The method is not invoked anywhere within the extension itself and therefore poses no direct risk in a default installati…

  • Medium 5.9

    Path Traversal in extension "Faceted Search" (ke_search)

    The file indexer does not normalize the configured directory path. A backend user with permission to edit indexer configurations can index documents from arbitrary locations on the server file system through path traversal sequences.

  • Medium 5.9

    Information Disclosure in extension "Faceted Search" (ke_search)

    The additional_tables configuration of the page and tt_content indexers accepts arbitrary table and field names. A backend user with permission to edit indexer configurations can copy sensitive data from internal TYPO3 tables into the search index.

  • Medium 5.9

    XML External Entity Injection in extension "Faceted Search" (ke_search)

    The OOXML parsing of the file indexer does not disable external entity resolution. A crafted xlsx or pptx document placed in an indexed directory can cause local files to be read or outbound HTTP requests to be performed, with the retrieved content being writ…

  • High 8.2
    CVE-2026-8726 Public exploit

    SQL Injection in extension "News system" (news)

    The extension fails to properly sanitize user input before using it in a database query. As a result, an unauthenticated attacker can inject arbitrary SQL through a URL parameter on pages using the "Date Menu of news articles" plugin. Exploitation requires th…

  • Medium 6.9

    Broken Access Control in extension "Frontend User Registration" (sf_register)

    The create and edit flows do not restrict which user properties may be submitted and do not enforce access control on the frontend user group assignment. As a result, an attacker can assign an arbitrary frontend user group to a newly registered or edited acco…

  • High 7.1

    Remote Code Execution in extension "Site Crawler" (crawler)

    The Crawler extension passes the X-T3Crawler-Meta response header from crawled URLs directly to PHP's unserialize(). An attacker controlling a crawled endpoint can inject arbitrary serialized PHP objects, leading to Remote Code Execution on the TYPO3 server. …

  • High 7.3

    TYPO3 CMS Stores Cleartext Password in User Settings Module

    Changing backend users' passwords via the user settings module results in storing the cleartext password in the uc and user_settings fields of the be_users database table. This issue affects TYPO3 CMS version 14.2.0.