CVE Vulnerability Catalog

In versions running on TYPO3 10 and 11, the configured OpenAI API key is embedded in every backend page so that the editor plugin can contact the OpenAI service directly from the browser. Any authenticated backend user can read the key and use it at the expense of the site operator. This only applies if an API key has been configured.

Values entered by visitors were placed into the HTML summary email without being escaped. An unauthenticated attacker could use this to inject HTML into an email that is shown to the recipient.

A weakness has been identified in Osclass up to 8.3.1. Affected is the function Item::findUserItems of the file oc-includes/osclass/model/Item.php of the Item Model Handler component. Manipulation of the sPattern argument causes SQL injection. The attack may be initiated remotely and the exploit has been made public. The vendor was contacted early but did not respond.

A security flaw has been discovered in mcollina mcp-ripgrep up to 0.4.0 in an unknown function of the file src/index.ts of the Advanced Search Tool component. Manipulation of the fileType argument results in OS command injection; the attack requires a local approach. The exploit has been released publicly and the real existence of this vulnerability is still doubted.

The download link for files uploaded through a form relied on a predictable token, and the file name in the request was not verified in a guess-resistant way. An unauthenticated attacker could access files uploaded by other visitors; the token was also shown in plain text in the text version of the notification email.

The extension provides a backend endpoint that writes a submitted value into a submitted field of a submitted page record. It neither checks the user's permissions nor limits which fields can be changed. Any authenticated backend user can therefore change any property of any page, including its access permissions and configuration, outside the scope granted to them.

The file search of the extension builds its database conditions by wrapping the search term in quotes itself. Only the wildcard characters of the LIKE operator are escaped, quote characters are not. A crafted search term can therefore leave the intended string value and change the database query, allowing an attacker to read data from the database. The issue affects every searched field.

The extension provides a public proxy endpoint that fetches a URL on behalf of the visitor. For one HTTP request method, the endpoint does not apply the authorization check protecting the other methods, so the fetched URL is fully controlled by the requester. An unauthenticated attacker can make the server send requests to arbitrary internal or external hosts and receives the status code and selected response headers, enabling probing of internal hosts and ports; response bodies are not disclosed.

The order cancellation function accepts an order identifier from the request and acts on that order without checking that the caller owns it. Any site visitor can set orders still awaiting payment to "canceled"; this requires a page containing the shop's order plugin. Orders that are already paid are not affected.

The AJAX routes of the extension do not check whether a backend user has access to the related module or dashboard widget. Any backend user can therefore retrieve analytics data of the sites they have page access to.

The extension no longer applied its access protection to files in file storages using a non-default relative base path. These files were served directly by the web server without authentication or permission checks. The issue is only exploitable when the extension is used on a website running TYPO3 14.3.

The backend module does not check whether a backend user has access to the requested site. Users with access to the module can therefore open the analytics dashboard of any site.

The extension hides the correct answer to each CAPTCHA inside the image data of the CAPTCHA itself. Anyone who can request a CAPTCHA image can read the answer from it and submit it, so automated clients can pass the challenge. This applies to the default configuration, because the audio feature that causes the answer to be embedded is enabled by default.

The JSON import of the cookie consent configuration did not respect the backend user's permissions. Non-admin backend users with access to the module could import a configuration that adds arbitrary scripts to the frontend of the website.

The routes that provide consent history and statistics data did not check whether the backend user had access to the module or to the requested page. Any authenticated backend user, regardless of permissions, could therefore retrieve consent data of any site in the installation.

The backend module for reviewing the consent history accepted sorting, grouping and index options from the request and used them in a database query without validation. Only the filter conditions of that query were bound as parameters. A backend user with access to the history or statistics functions could use this to read arbitrary data from the database, including password hashes of backend and frontend users.

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Brizy Brizy brizy allows Stored XSS. This issue affects Brizy: 2.8.23.

The vulnerability in Apache C++ Parquet and PyArrow versions 4.0.0 to 25.0.1 involves pass-through of unvalidated KMS URLs to KMS clients. If the user does not leverage application control for this parameter, a file-controlled KMS URL is forwarded to a pluggable KmsClient implementation, potentially sending a KMS token to a malicious host.

A vulnerability in the bulk port configuration functionality could allow an unauthenticated attacker to crash the service.

A vulnerability in the proprietary protocol could allow an attacker to brute force the administrator password without restrictions, even when the SafeEnhancement feature is enabled.