Larlarua

Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Versions prior to 2.17.1 expose `log js errors` to any authenticated user, including guest users when guest access is enabled. The endpoint writes attacker-controlled strings directly into the main application log. The administrator-only `logFile` view then reads that log file and embeds it into an HTML response without escaping. This creates a stored cross-site scripting condition where a low-privilege guest can inject HTML or JavaScript into the log file and have it execute in an administrator's browser when the log viewer is opened. Version 2.17.1 patches the issue.

**Name of the Vulnerable Software and Affected Versions** Tautulli versions prior to 2.17.1 **Description** Tautulli contains a Server-Side Request Forgery (SSRF) issue where a public endpoint '/image/<hash>' resolves entries from `image hash lookup` and processes them using the same server-side image fetch logic as authenticated image proxying. A low-privilege guest user can insert a malicious external image URL into the lookup table, allowing any unauthenticated external user to trigger server-side fetches to an arbitrary attacker-chosen URL by requesting '/image/<hash>.png'. SSRF is a flaw that allows an attacker to induce the server-side application to make requests to an unintended location. **Recommendations** Update to version 2.17.1.

Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Versions prior to 2.17.1 expose `configUpdate` as a state-changing administrator endpoint, but the route does not enforce `POST` and does not use any anti-CSRF token. In the default form and JWT-based authentication mode, the administrator session cookie is issued with `SameSite=Lax`, which still permits top-level cross-site navigation requests. An attacker can exploit this by luring a logged-in administrator to a malicious page that submits a cross-site request to `/configUpdate` and overwrites the local administrator username and password. The attacker can then sign in directly with the chosen credentials and take over the Tautulli administrative interface. Version 2.17.1 patches the issue.

**Name of the Vulnerable Software and Affected Versions** Froxlor versions prior to 2.3.7 **Description** An issue exists where server-side FTP account handlers do not enforce the `system.available shells` whitelist when processing add or edit requests. This allows an authenticated customer with shell delegation enabled to submit an arbitrary shell, such as `/bin/bash`, bypassing the restricted choices presented in the panel UI. In deployments using the default `nssextrausers` integration, the attacker-controlled shell is propagated into the system account database, granting real host shell access. The flaw occurs because the `Ftps::add()` and `Ftps::update()` functions perform only generic string validation instead of verifying the shell against the approved list. This can be exploited via the `/customer ftp.php` endpoint by manipulating the `shell` parameter. **Recommendations** Update to version 2.3.7. As a temporary workaround, restrict the use of the `shell` parameter in the `/customer ftp.php` endpoint or disable customer shell delegation by setting `system.allow customer shell` to 0.

**Name of the Vulnerable Software and Affected Versions** Froxlor version 2.3.6 **Description** A symlink-following flaw exists in the root-owned SSH key synchronization path used for customer FTP users. The provisioning code appends public keys to `~/.ssh/authorized keys` within a customer-controlled home directory without verifying if the target path is a symbolic link. An attacker with a shell-enabled customer account can replace `~/.ssh/authorized keys` with a symlink pointing to `/root/.ssh/authorized keys`. When the privileged cron task executes the `SshKeys::generateFiles()` function and subsequently appends the key, the attacker-supplied key is added to the root user's authorized key file, granting the attacker root SSH access. This process involves the `SshKeys.add` API call and the `makeCorrectFile()` function, which fails to resolve or reject symlinks. **Recommendations** Update to version 2.3.7.

**Name of the Vulnerable Software and Affected Versions** OpenReplay versions prior to 1.26.0 **Description** OpenReplay is a self-hosted session replay suite. The Python API contains several 'app apikey' routes that trust a caller-provided `projectKey` after verifying only the validity of the API key and the existence of the target `projectKey`. The authorization flow fails to verify that the authenticated API key and the requested project belong to the same tenant. Since the public tracker design exposes the `projectKey` to browser-side code, an attacker with a valid API key for their own tenant can use another tenant's public `projectKey` to enumerate victim user sessions and retrieve sensitive session event data across tenant boundaries. **Recommendations** Update to version 1.26.0.

**Name of the Vulnerable Software and Affected Versions** SillyTavern versions prior to 1.18.0 **Description** SillyTavern is a locally installed user interface for interacting with large language models, image generation engines, and text-to-speech models. The application contains a Server-Side Request Forgery (SSRF) issue—a flaw where a server is tricked into making requests to an unintended location—via the '/api/search/searxng' endpoint. An authenticated low-privilege user can provide a malicious `baseUrl` variable, which the server uses to build outbound fetches without performing allowlist, IP range, DNS, or scheme validation. This allows an attacker to point the request toward internal or loopback HTTP services and receive the response body, potentially disclosing information from internal admin panels, development services, or cloud metadata endpoints. **Recommendations** Update to version 1.18.0. Enable and properly configure the Private Request Whitelisting filter, especially when the instance is hosted over a network.

**Name of the Vulnerable Software and Affected Versions** BentoML versions prior to 1.4.39 **Description** The `bentoml build` packaging workflow follows attacker-controlled symlinks within the build context and copies the referenced file contents into the generated Bento artifact. This occurs because the system does not validate if the resolved path of a file remains inside the build context before dereferencing the source path. An attacker can place a symlink pointing to sensitive local files on the build host, such as cloud credentials, SSH keys, API tokens, or environment files. When the build process runs, these files are packaged into the Bento artifact and can be further leaked through export, push, or containerization workflows. **Recommendations** Update to version 1.4.39.

**Name of the Vulnerable Software and Affected Versions** Chartbrew versions prior to 5.0.0 **Description** Chartbrew exposes a legacy dashboard route that returns a project's report data to any authenticated member of the same team, regardless of whether the user has access to that specific project. This occurs because the route bypasses project-level authorization and returns the raw project object. Consequently, a low-privileged user within the same team can read dashboard data from another project and recover the stored report password from the response. **Recommendations** Update to version 5.0.0.

**Name of the Vulnerable Software and Affected Versions** Chartbrew versions prior to 5.0.0 **Description** Chartbrew exposes public chart retrieval and export routes that only verify project-level public access and a team-level export toggle. These routes fail to verify if the target chart is allowed on the public report or if the governing `SharePolicy` permits public access. Consequently, an unauthenticated attacker with a chart identifier in a public project can read or export data for charts intentionally hidden from the report. **Recommendations** Update to version 5.0.0.

**Name of the Vulnerable Software and Affected Versions** Chartbrew version 4.9.0 **Description** Chartbrew allows authenticated users with access to one project to update or delete a SharePolicy record belonging to a different project. The application authorizes the caller based on the project in the URL path but fails to verify if the `policy id` belongs to that specific project. This enables cross-project modification of dashboard sharing rules, including visibility, password requirements, allowed parameters, and expiration settings. **Recommendations** Update to version 5.0.0.

**Name of the Vulnerable Software and Affected Versions** Chartbrew versions prior to 5.0.0 **Description** Chartbrew is an open-source web application used to create charts by connecting to databases and APIs. The application exposes the "POST /api/chart/:chart id/query" endpoint without authentication. The system only verifies the `team.allowReportRefresh` setting and fails to check if the target chart belongs to a public report, if the project is public, or if the sharing policy permits the operation. An unauthenticated attacker with a chart identifier can trigger a data refresh and retrieve current data from private charts. **Recommendations** Update to version 5.0.0.

**Name of the Vulnerable Software and Affected Versions** Chartbrew versions prior to 5.0.0 **Description** Chartbrew exposes multiple 'dataset' and 'dataRequest' endpoints that authorize low-privileged project members at the team level. The system fails to bind the requested `dataset id`, `dataRequest id`, and `connection id` to the projects allowed for the caller. This allows an authenticated attacker with access to a single project within a team to read, execute, create, update, and delete datasets and data requests belonging to other projects in the same team. This leads to cross-project data disclosure and unauthorized use of database or API connections. **Recommendations** Update to version 5.0.0.

**Name of the Vulnerable Software and Affected Versions** JeecgBoot versions prior to 3.9.1 **Description** A remote SQL injection is possible via the 'loadDict' endpoint. The issue exists within the `SqlInjectionUtil()` function located in the file jeecg-boot/jeecg-boot-base-core/src/main/java/org/jeecg/common/util/SqlInjectionUtil.java, where improper manipulation of the `keyword` argument allows for the attack. **Recommendations** Deploy patch a9c8e8eb1185751c4c3c68d2a53f3dadee9edc6b. As a temporary workaround, restrict access to the 'loadDict' endpoint to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Xuxueli xxl-job versions prior to 3.3.3 **Description** An issue exists in the OpenAPI Endpoint within the file `xxl-job-admin/src/main/java/com/xxl/job/admin/scheduler/openapi/OpenApiController.java`. Manipulation of the `default token` argument leads to the use of a hard-coded cryptographic key. This flaw allows for remote attacks, although it is characterized by high complexity and difficult exploitability. **Recommendations** Update to a version newer than 3.3.2. As a temporary workaround, restrict access to the `default token` argument in the OpenAPI Endpoint to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Xuxueli xxl-job versions prior to 3.3.3 **Description** A server-side request forgery (SSRF) exists in the 'trigger' endpoint. The issue resides in the `triggerJob()` function within the file `xxl-job-admin/src/main/java/com/xxl/job/admin/service/impl/XxlJobServiceImpl.java`, where improper manipulation of the `addressList` argument allows a remote attacker to initiate unauthorized requests. SSRF is a flaw that allows an attacker to induce the server-side application to make requests to an unexpected destination. **Recommendations** Update to a version later than 3.3.2. As a temporary workaround, restrict access to the 'trigger' endpoint and ensure strict access control for the `triggerJob()` function.

**Name of the Vulnerable Software and Affected Versions** Xuxueli xxl-job versions prior to 3.4.0 **Description** A security flaw exists in the Execution Log Handler component within the `logDetailCat()` function of the `JobLogController.java` file. Remote manipulation of the `logId` argument leads to improper control of resource identifiers. This issue is characterized by high complexity and difficult exploitability. **Recommendations** Upgrade to version 3.4.0. As a temporary workaround, restrict access to the `logDetailCat()` function to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** o2oa versions prior to 10.0 **Description** An improper authorization issue exists in the NodeAgent component within the `syncFile()` function of the NodeAgent.java file. This flaw allows a remote attacker to initiate an attack, although the complexity is high and exploitability is considered difficult. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability. As a temporary workaround, consider restricting the use of the `syncFile()` function within the NodeAgent component to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** o2oa versions prior to 10.0 **Description** A flaw in the URL Fetching component allows for remote server-side request forgery (SSRF), which occurs when a server is tricked into making requests to an unintended location. This issue exists within the `FileAction()` function of the `FileAction.java` file and is triggered by manipulating the `fileUrl` argument. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability. As a temporary workaround, restrict access to the `FileAction()` function or the URL Fetching component to minimize the risk of exploitation.