CVE-2025-65795: Incorrect access control in the /api/v1/user endpoint of usememos memos v0.25.2 allows unauthorized attacke...
Incorrect access control in the /api/v1/user endpoint of usememos memos v0.25.2 allows unauthorized attackers to create arbitrary accounts via a crafted request.
Security readout for executives and security teams
Plain-English summary
Memos v0.25.2 has an access-control flaw that can let an unauthenticated outsider create accounts through the user API. The main business risk is unauthorized account creation and loss of control over who can access or modify the service.
Executive priority
Treat this as a high-priority identity and access-control issue for any exposed memos instance. Urgency is highest where the service contains sensitive team notes or grants privileges after account creation.
Technical view
The issue is CWE-284 incorrect access control in /api/v1/user. CVSS 3.1 is 7.5, network exploitable, low complexity, no privileges, no user interaction, with high integrity impact and no stated confidentiality or availability impact.
Likely exposure
Internet-facing or internally reachable usememos memos v0.25.2 deployments are most exposed, especially where account creation should be restricted. The source bundle does not identify CPEs or broader affected versions beyond v0.25.2.
Exploitation context
The CVE describes crafted unauthenticated requests creating arbitrary accounts. The bundle marks KEV false and provides no cited evidence of active exploitation, public exploit use, or weaponized tooling.
Researcher notes
Evidence is limited to the CVE description, CVSS vector, CWE, and two references. The bundle does not name a fixed release, confirm exploitation, or enumerate affected versions beyond memos v0.25.2.
Mitigation direction
Identify memos deployments and prioritize any running v0.25.2.
Check the vendor PR and advisory for fixed-version guidance.
Apply the vendor-provided fix when confirmed available.
Restrict external access to affected memos instances until remediated.
Review and remove unauthorized accounts created during exposure windows.
Validation and detection
Confirm whether any deployed memos instance is version v0.25.2.
Review configuration and logs for unexpected account creation events.
Verify remediation status against vendor PR or advisory guidance.
Retest access control only in an authorized test environment.
Document exposed instances, remediation dates, and residual exceptions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.