| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Pleasanter contains an issue with improper limitation of a pathname to a restricted directory ('Path Traversal') in the API. If this vulnerability is exploited, an arbitrary file on the server where the product is running may be obtained by a remote authenticated attacker. |
| Pleasanter contains an incorrect authorization vulnerability in the access control of Items. If this vulnerability is exploited, a remote authenticated attacker who can view records in the affected product may obtain the values of Items for which read access is restricted by Column access control. Note that the vulnerability affects configurations where read access conditions are set in Column access control settings. |
| OpenVPN 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows allows local authenticated users to execute arbitrary code via a privileged service using user-controlled environment variables. |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Build Features page was possible |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Slack Notifier settings page was possible |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in implicit agent requirements was possible |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project Import |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possible |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 code injection in parent project Kotlin DSL was possible via subproject settings |
| In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 command injection in Project Import artifact copy scripts was possible |
| In JetBrains TeamCity before 2026.2.2 a CSRF attack was possible on the diagnostic page |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in the enforced settings restriction tooltip was possible |
| In JetBrains TeamCity before 2026.2.2 stored XSS in external change viewer links was possible |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Projects Import page was possible |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via commit messages |
| flowintel allows users with editor-level access to author case and task fields, including aggregated tags. When these records are exported as CSV, the field values are written verbatim into the output file.
Because no sanitisation is applied to user-supplied text before CSV serialisation, an attacker can store values that begin with spreadsheet formula triggers (such as =, +, -, @, or their fullwidth Unicode equivalents, or leading control/whitespace characters). When a victim opens the exported CSV in a spreadsheet application (e.g. Microsoft Excel, LibreOffice Calc), the stored text is interpreted and executed as a live formula rather than displayed as literal text.
This can lead to unintended data manipulation within the spreadsheet, potential data exfiltration via formula functions, or execution of downstream commands depending on the spreadsheet application and its configuration.
The vulnerability requires the victim to actively open the CSV file in a spreadsheet application; the flowintel application itself is not directly compromised.
Affected: <4.1.0 |
| MISP contains an authorization flaw in the sharing group capture logic. When a sharing group is re-captured with a newer modified timestamp and an updated roster, the application unconditionally overwrote the type, nationality, sector, and contacts fields of every organisation listed in the roster, including the host organisation. This behaviour was reachable by any user holding the perm_sync role, and additionally by any external server pulled from or any feed fetched, because those operations execute with the privileges of the site administrator who initiated them. As a result, a low-privileged sync user or a malicious/compromised external feed or pull source could silently corrupt organisation records on the receiving MISP instance without any site-admin or internal-sync authorization. The vulnerability does not disclose data or affect availability; the impact is limited to integrity of organisation metadata (type, nationality, sector, contacts). The fix restricts organisation detail updates to internal sync operations (pulls over links flagged as internal, or senders holding perm_sync_internal) and site administrators; all other sync, pull, and feed operations may only match existing organisations by UUID or create new ones, without modifying their stored details. |