Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
8DescriptionCVE.org
A weakness has been identified in usememos memos up to 0.22.1. This affects the function memos_access_token of the file src/App.tsx of the component UpdateInstanceSetting. This manipulation of the argument additionalStyle/additionalScript causes improper authorization. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
AnalysisAI
Improper authorization in usememos memos up to version 0.22.1 allows authenticated remote attackers to bypass access controls via manipulation of additionalStyle and additionalScript arguments in the UpdateInstanceSetting component, potentially leading to unauthorized information disclosure, modification, and service disruption. The vulnerability has publicly available exploit code and affects the memos_access_token function in src/App.tsx. The vendor did not respond to early disclosure efforts.
Technical ContextAI
The vulnerability resides in the UpdateInstanceSetting component's handling of the memos_access_token function within src/App.tsx. The root cause is classified as CWE-285 (Improper Authorization), indicating that the application fails to properly validate or enforce access controls when processing user-supplied arguments (additionalStyle and additionalScript). These arguments are likely passed to a function or API endpoint that should enforce role-based or capability-based authorization checks, but instead accepts them without proper validation of the caller's permissions. The attack vector is network-based with low attack complexity, suggesting the vulnerability can be exploited through standard HTTP requests without requiring special techniques or bypassing additional security layers. The affected product is usememos memos, a note-taking or memo management application (CPE: cpe:2.3:a:usememos:memos:*:*:*:*:*:*:*:*), with all versions up to and including 0.22.1 confirmed vulnerable.
RemediationAI
Upgrade usememos memos to a version newer than 0.22.1 immediately. Check the project's official GitHub repository (https://github.com/usememos/memos) for the latest released version with authorization fixes applied. If a specific patched version number is not yet available in the project's releases, monitor the repository's release notes or security advisories for confirmation of a fix. As a temporary compensating control pending patching, restrict network access to the UpdateInstanceSetting endpoint and memos application to trusted internal IP addresses or VPN-only access, reducing the attack surface to authenticated users on the internal network; this does not eliminate the vulnerability but limits exposure to insider threats. Additionally, enforce strong authentication mechanisms (multi-factor authentication, single sign-on with centralized identity management) to reduce the likelihood that stolen or weak credentials enable unauthorized access. Monitor memos access logs for suspicious UpdateInstanceSetting API calls, particularly those modifying additionalStyle or additionalScript parameters by low-privilege accounts; any suspicious activity should trigger credential rotation for affected users. If patching is delayed, consider disabling the UpdateInstanceSetting feature entirely if it is not critical to operations, though this may require custom code modification. Do not rely solely on network segmentation; the primary mitigation is patching to a secure version.
elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplie
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.0. Rated critical seve
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.1. Rated critical severity (CVSS 9.
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.1. Rated critical severity (CVSS 9.
Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.15.1. Rated high severity (CVSS 8.8), t
Improper Privilege Management in GitHub repository usememos/memos prior to 0.13.2. Rated high severity (CVSS 8.8), this
Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.9.1. Rated high severity (CVSS 8.8), th
Improper Access Control in GitHub repository usememos/memos prior to 0.9.1. Rated high severity (CVSS 8.8), this vulnera
Improper Privilege Management in GitHub repository usememos/memos prior to 0.9.1. Rated high severity (CVSS 8.8), this v
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.1. Rated high severity
Improper Access Control in GitHub repository usememos/memos prior to 0.9.0. Rated high severity (CVSS 8.8), this vulnera
Improper Authorization in GitHub repository usememos/memos prior to 0.9.0. Rated high severity (CVSS 8.8), this vulnerab
Same weakness CWE-285 – Improper Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-23838
GHSA-gqp3-hfc3-8q54