Filtered by vendor Usememos
Subscriptions
Total
60 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2022-4798 | 1 Usememos | 1 Memos | 2024-11-21 | 5.3 Medium |
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.1. | ||||
CVE-2022-4797 | 1 Usememos | 1 Memos | 2024-11-21 | 4.3 Medium |
Improper Restriction of Excessive Authentication Attempts in GitHub repository usememos/memos prior to 0.9.1. | ||||
CVE-2022-4796 | 1 Usememos | 1 Memos | 2024-11-21 | 8.1 High |
Incorrect Use of Privileged APIs in GitHub repository usememos/memos prior to 0.9.1. | ||||
CVE-2022-4767 | 1 Usememos | 1 Memos | 2024-11-21 | 7.5 High |
Denial of Service in GitHub repository usememos/memos prior to 0.9.1. | ||||
CVE-2022-4734 | 1 Usememos | 1 Memos | 2024-11-21 | 8.1 High |
Improper Removal of Sensitive Information Before Storage or Transfer in GitHub repository usememos/memos prior to 0.9.1. | ||||
CVE-2022-4695 | 1 Usememos | 1 Memos | 2024-11-21 | 5.4 Medium |
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4694 | 1 Usememos | 1 Memos | 2024-11-21 | 5.4 Medium |
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4692 | 1 Usememos | 1 Memos | 2024-11-21 | 5.4 Medium |
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4691 | 1 Usememos | 1 Memos | 2024-11-21 | 5.4 Medium |
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4690 | 1 Usememos | 1 Memos | 2024-11-21 | 5.4 Medium |
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4689 | 1 Usememos | 1 Memos | 2024-11-21 | 8.8 High |
Improper Access Control in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4688 | 1 Usememos | 1 Memos | 2024-11-21 | 8.8 High |
Improper Authorization in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4687 | 1 Usememos | 1 Memos | 2024-11-21 | 8.1 High |
Incorrect Use of Privileged APIs in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4686 | 1 Usememos | 1 Memos | 2024-11-21 | 9.8 Critical |
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4684 | 1 Usememos | 1 Memos | 2024-11-21 | 8.8 High |
Improper Access Control in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4683 | 1 Usememos | 1 Memos | 2024-11-21 | 6.5 Medium |
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-4609 | 1 Usememos | 1 Memos | 2024-11-21 | 5.4 Medium |
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.0. | ||||
CVE-2022-25978 | 1 Usememos | 1 Memos | 2024-11-21 | 5.4 Medium |
All versions of the package github.com/usememos/memos/server are vulnerable to Cross-site Scripting (XSS) due to insufficient checks on external resources, which allows malicious actors to introduce links starting with a javascript: scheme. | ||||
CVE-2023-0109 | 1 Usememos | 1 Memos | 2024-11-19 | 5.4 Medium |
A stored cross-site scripting (XSS) vulnerability was discovered in usememos/memos version 0.9.1. This vulnerability allows an attacker to upload a JavaScript file containing a malicious script and reference it in an HTML file. When the HTML file is accessed, the malicious script is executed. This can lead to the theft of sensitive information, such as login credentials, from users visiting the affected website. The issue has been fixed in version 0.10.0. | ||||
CVE-2024-41659 | 1 Usememos | 1 Memos | 2024-08-22 | 8.1 High |
memos is a privacy-first, lightweight note-taking service. A CORS misconfiguration exists in memos 0.20.1 and earlier where an arbitrary origin is reflected with Access-Control-Allow-Credentials set to true. This may allow an attacking website to make a cross-origin request, allowing the attacker to read private information or make privileged changes to the system as the vulnerable user account. This vulnerability is fixed in 0.21.0. |